Notifications
Announcements
No record found.
I am trying to determine which tables, in case I wrote a script for the customer, I would need to update - My customer has a Salesperson retiring and so they want to move all of his customers to another existing salesperson. I was looking at the RM00102 TABLE as one that would need to be updated but are there any other tables that we would need to update as well?
Using GP Power Tools Resource Information window, I can tell you that based on a core Dynamics GP install (not with the same addon products you might have), the 'Saleperson ID' field appears in 32 tables.
There is also the 'Start Salesperson ID' and 'End Salesperson ID' field.
Using the Resource Finder window we could actually identify exactly which tables your retiring Salesperson exists in and then a simple SQL Update Statement can change the ID to their replacement.
To do this all manually, without the field filtering and many other features offered by GP Power Tools, you could look at the following article:
winthropdc.wordpress.com/.../
Regards
David
Thanks Dave - they probably do not want to change the History tables. They want some kind of a script to update the retiring Salesperson to the new one instead of assigning each customer to the new salesperson in GP.
If you have access to SQL, run this script on your Database. It will show you every table that has the field name you are wanting to update and where it is located.
SELECT DISTINCT
TABLE_NAME
FROM
INFORMATION_SCHEMA.COLUMNS WHERE COLUMN_NAME = 'slprsnid'
The PSTL Salesperson Modifier is a great tool if you want everything assigned to the retiring salesperson now assigned to the new salesperson:
Excellent Suggestion Lisa..... why re-invent the wheel?
I haven't used this tool in a long time but I believe it changes all the transaction history ... Works great if you want to be able to compare a customer's salesperson history over time, but can be confusing if that isn't the expected behavior. I have often updated the customer/customer address tables via SQL to default in the new salesperson going forward when the history needed to not be changed.) As you remind us often, testing and backups are your best friends when manipulating data.
That was one of the first things I looked at but if it changed the ID then as long as that user was setup as a salesperson already then it would work but I am not sure if they want to change all the history tables though
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 660 Most Valuable Professional
André Arnaud de Cal... 549 Super User 2025 Season 2
Sohaib Cheema 307 User Group Leader