Question Status

Verified
Mark E asked a question on 21 Jul 2014 12:42 PM

Trying to customize the above screen, but it can only be launched from the OM Shipment Confirmation screen (40.117.00).  In SL7 and prior versions, it was possible to launch the screen, then use Task Manager to close the 40.117.00 screen, then launch CU.  Now, in SL2011, this is no longer possible, the Message 6805 occurs (Only one application may be executing when customization mode is started).

It is also not possible to launch the 50.002.00 screen directly via Windows Explorer, as it throws message 15840 (No Shipper Id supplied. Exiting).  So, my question is, where exactly does SL look to determine if there are other open Application screens?  I tried to remove the record from the Access table, but that did not work either..

Does it look somewhere else to determine this, and trigger the 6805 message?  How can I customize the 50.002.00 screen now?

Reply
Verified Answer
Mark E responded on 23 Jul 2014 2:37 PM

The resolution is to first enable Initialize Mode in SL, then use Windows Explorer to launch the 50.002.00 screen, which avoids the ShipperID parameter requirement.

Reply
Suggested Answer
PerumalSamy R responded on 22 Jul 2014 6:59 AM

Hello Mark E,

To my knowledge, SL doesn’t store the value while doing the customization check. I’m suggesting below steps to do the customization in container builder.

  1. Close all the open SL screen if exists
  2. Go to the Solomon Root folder and open the AN folder
    1. For example path “C:\Program Files (x86)\Microsoft Dynamics\SL\Applications\AN”
    2. Open the 50.002.00 screen and Press CTL+ALT+C
    3. start doing your customization in container builder screen.

Hope this explains.

Thanks,

Perumalsamy R

Reply
Suggested Answer
PerumalSamy R responded on 22 Jul 2014 6:59 AM

Hello Mark E,

To my knowledge, SL doesn’t store the value while doing the customization check. I’m suggesting below steps to do the customization in container builder.

  1. Close all the open SL screen if exists
  2. Go to the Solomon Root folder and open the AN folder
    1. For example path “C:\Program Files (x86)\Microsoft Dynamics\SL\Applications\AN”
    2. Open the 50.002.00 screen and Press CTL+ALT+C
    3. start doing your customization in container builder screen.

Hope this explains.

Thanks,

Perumalsamy R

Reply
Mark E responded on 22 Jul 2014 7:51 AM

Perumal,

As I mentioned in my post, that is not an option, as the screen throws message 15840 (No Shipper Id supplied. Exiting) when it is not launched from the Shipment Confirmation screen.  

The ShipperID parameter is required to be passed in order to successfully open the screen.

Reply
PerumalSamy R responded on 22 Jul 2014 8:36 AM

Mark E,

I tried the same way that I suggested in my 2011 local environment and it works for me. I believe your container builder is already customized.

Thanks,

Perumalsamy R

Reply
Mark E responded on 22 Jul 2014 9:10 AM

That message is not from a screen customization, I can see it in the source code pdf.  I cannot get the screen to successfully launch without a ShipperID parameter being passed.  See below.

serr1 = SqlFetch1(csr_SOShipHeader, "SOShipHeader_All " & SParm(bInputParms.CpnyID) & SParm(bInputParms.ShipperID), bSOShipHeader)

If serr1 <> NOTFOUND Then

Call DispField(crefnbr)

Call DispField(cSiteId)

Call DispField(ctareid_0)

Call DispField(CType(frm5000220.Controls("crefnbr2"), Object))

Call DispField(CType(frm5000220.Controls("cSiteId2"), Object))

If bSOShipHeader.Status = "C" Then

Call DisplayMode(True)

End If

' Read in the BOL number so that we can assign to each container

serr1 = SqlFetch1(csr_EDContainer4, "EDShipTicket_BOLNumber" & SParm(bSOShipHeader.CpnyID) & SParm(bSOShipHeader.ShipperID), bBOLNbr)

Else

Call Mess(15840)

Call screenexit("", "")

End If

Reply
PerumalSamy R responded on 22 Jul 2014 10:59 AM

Mark E,

Is your code written in form_load event of container builder screen?

Are you trying to customize the container builder screen from Shipment confirmation screen?

If yes, you can not do the container builder customization from Shipment confirmation screen since container builder screen is a standalone SL screen.

Thanks,

Perumalsamy R

Reply
Mark E responded on 22 Jul 2014 11:04 AM

Perumal,

You are completely missing the point of what I am saying.  The code I posted above is NOT from any screen customization, but it is a snippet of the source code that does not allow the screen to open unless the ShipperID parameter is passed to it when opening.

The screen cannot be opened by itself.

Reply
Verified Answer
Mark E responded on 23 Jul 2014 2:37 PM

The resolution is to first enable Initialize Mode in SL, then use Windows Explorer to launch the 50.002.00 screen, which avoids the ShipperID parameter requirement.

Reply