Customer Maintenance - Import new values for Territory ID?

(0) Share

Report

Posted on by TomR

I am a new employee and new to GP (2010). My company wants to change each Customer card's 'Territory ID' from the current value ('ALL') to one of 4 newly defined territories. I would like to create a spreadsheet with the customer number and new territory code then upload the changes to GP. I just want to update the value of the 1 field.

Is there an easy way to do this?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Praveen Kumar RR 1,552 on at

Like (0)

Report
Copy link

Link copied!

SQL Update option should be helpful

Was this reply helpful? Yes No
Suggested answer

Tim Wappat 5,713 on at

Like (1)

Report
Copy link

Link copied!

I would recommend you search on

Dynamics GP Macro Mail Merge

and watch some of the YouTube videos and blogs around this subject.

Dynamics GP has a macro system that allows you to record actions on screen and replay them, you can use MS Word to then repeat these actions but changing data as you do. In this case allowing each customer to be updated with a different Territory ID.

This is a good end user option for mass changes of data, that is less risky than SQL updates, as it enforces all the business rules of the GP user interface. It is amazing how often I find there is some nuance about use of values in fields that the uesr interface hightlights, but I would have been unaware of if I'd just gone and changed it in the database!

Tim

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (1)

Report
Copy link

Link copied!

GPUG had a training class scheduled for this Thursday (2/2/17) devoted to Macros. The class is a hands on, build your own macros, kind of class that covers not only the Mail-Merge macro, but also using the Macro language with scrolling windows. It covers other Macro related tips, but the best part is that you get some exercises so that you can use all of the features yourself.

Kind regards,

Leslie

Was this reply helpful? Yes No
Suggested answer

Victoria Yudin 22,769 on at

Like (0)

Report
Copy link

Link copied!

I vote for a SQL update. This is a perfect example of data that is not tied to anything else except the new Territory ID already existing in GP. Just wrote a blog about this: victoriayudin.com/.../updating-dynamics-gp-data-directly-in-sql

Was this reply helpful? Yes No
Tim Wappat 5,713 on at

Like (1)

Report
Copy link

Link copied!

Yes this is a good example of an isolated field, perfect for SQL update, but that is knowledge based on our experience with GP.

I would still recommend using macros, for those less experienced with the GP data model, or before you know it, the IT department are getting over confident about what they can change in the database through SQL on any request from users...

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report
Copy link

Link copied!

Tim,

I think your cautions are well stated. Some of these SQL updates/changes are simple - but only if you know the data model. I have had client IT department folks watch me do something and then do the 'same thing' in a different area thinking it would be the same. Unfortunately, it's usually not the same. I like the advice you give for users who might not be as knowledgeable about the data model.

Thank you for highlighting this difference.

Leslie

Was this reply helpful? Yes No