web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Shipping Method not Rolling down

(0) ShareShare
ReportReport
Posted on by

Hi All,

I have a customer that recently moved all their data from one database to another.  They sold the company but are still using the same server with GP.   They just created a new company in GP and migrated the data over.  They did this internally, so I don't have all the details as to how they did it.

Ever since they have moved to this database, when they put in a sales order (using SOP) and change the shipping method on the header they get the following error message: The Customer Address could not be updated for one or more lines.  Update the customer address at the line level.   They are not changing the address, just the shipping method.  When I looked at the order, the shipping method had not changed at the line item level.  Further testing shows this ONLY happens to new customers since the migration.

Does anyone have any ideas as to what may be causing this?

Thanks in advance for your help,

Kathy

*This post is locked for comments

I have the same question (0)
  • coquisalsa Profile Picture
    2,725 on at

    Has the Sales Transaction Entry form been customized? If it has, first thing to try is switching off the customizations for this form using: Dynamics GP > Setup > System > Alternate/Modified Forms and Forms and test it again. This will help you to determine if the issue is related to a customized form.

    If the error persist let me know and I will look into further, but first try my above suggestion.

  • Community Member Profile Picture
    on at

    The form has not been modified.  Thanks

  • Suggested answer
    coquisalsa Profile Picture
    2,725 on at

    Create a Script.log, this might help you to determine why you are getting the message:

    Log out of GP and change the Dex.ini switch ScriptDebugger=TRUE

    Log back into GP, there will be a DEBUG menu in the toolbar

    Go to the SOP Sales Debtor Detail Entry right before where you want to start logging

    Click Debug >> Log Script

    Change the shipping method in the header

    Stop the logging by clicking on debug/Log Scripts again

    The log file will be in the GP install Data Folder and be named script.log

    The message you are getting is a standard GP message and its Message ID is 8309

  • Community Member Profile Picture
    on at

    I've attempted to follow the suggestion of turning on the script debugger, but there isn't that option in the Dex.ini     Is this an additional module I need to install?

  • coquisalsa Profile Picture
    2,725 on at

    If the switch ScriptDebugger is not in the Dex.ini, you can add it at the end of the file.

  • Community Member Profile Picture
    on at

    Hi Jorge,

    I was able to add the script debugger, and create a script.  It is referencing Rockton_helper throughout the whole script log.   Other than that, I'm not seeing a whole lot that makes sense to me.  The customer does have the Rockton GP Toolbox product, but not sure if that is what it's referencing.  They have changed their system password, so I'm working on getting the new password so I can disable the Rockton product.  Any other advice?

    Thanks,

    Kathy

  • Suggested answer
    Bill Campbell Profile Picture
    12 on at

    Kathy, I have seen this in other instance and not with Rockton necessarily, but at some point it is possible that someone had Rockton installed on the sample compnay database.

    At this point, you need to check out the Dynamics.Set and see if you can account for all the modules and 3rd Parties.

    In the event you find nothing in the Dynamics Set, you are going to have to see if there are 'rouge' tables in the database - often the case - if you move data over and do not install all the 'same' modules you can get this kind of error.

    Have a look and see what you can find.

  • Suggested answer
    coquisalsa Profile Picture
    2,725 on at

    Hi Kathy,

    You can use the 'Customisation Status' window to disable GP products:

    Microsoft Dynamics GP > Tool > Customise

    This might help you to find the root of the problem.

  • Suggested answer
    Bill Campbell Profile Picture
    12 on at

    Jorge. That is a great idea.  You are correct this should assist in getting to the root of the problem quicker, but only if the Rockton software code is loaded on the workstation you are working with.

  • Community Member Profile Picture
    on at

    This is a great idea, unfortunately, it still didn’t fix the issue.  I disabled everything except core GP and still got the error.

    I’ve also checked the .set file and all looks good there.

    I’ll check with the customer on the idea of whether they didn’t install a particular module in the new db and look for rogue tables.

    Thanks for all the help and if you have any more ideas, please let me know.

    Kathy

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

#2
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans