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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Connector: GP Pricing to CRM Price List Item

(0) ShareShare
ReportReport
Posted on by

I'm working on integrating GP 2013 with CRM Online.  I have the most up to date version of the Dynamics Connector.  The issue I'm having is with the GP Pricing to CRM Price List Item map.  The map runs without error but not everything integrates over.  There are 11 price lists total.  All 11 of the Price List Headers have been successfully integrated.  When the Price List Item map runs, only 1 price list has all (or at least most) of the 2200 price list lines.  The other 10 price lists only have around 90 price list lines (they appear to be the same 90 inventory items).  I deleted all the price list items from the CRM price lists and reran the map for all GP data (Data entered after 1/1/1900) and I received the same results with the only difference being the price list that had all of the items was a different price list than the first time.  (For example, on the first attempt, price list 1 had all the lines and 2 through 11 only had the 90 line and on the second attempt, price list 1 through 9 had 90 lines, price list 10 had all the lines, and price list 11 had 90 lines).  On subsequent runs on the map, nothing else integrates over.  I've searched and searched and I'm not sure where to look at this point.

 

Thanks!

*This post is locked for comments

I have the same question (0)
  • Michael Siegel Profile Picture
    25 on at

    I've got something similar going on between GP 2013 and CRM 2011.

  • RCCHULUOTA Profile Picture
    on at

    Working on the issue yesterday, I discovered that if I make and save a change to the price list for an item (in GP) that currently doesn't appear on all but the one of the CRM price lists, the next time the connector syncs, it picks up that change and adds it to the price levels that were changed on the GP price list.  I'm trying to dig deeper to see what exactly the connector is looking for to determine a change and what GP is changing (if anything) besides that actual data.  I'm not due if the DEX_ROW_TS column plays into anything relating to the connector.  I'll certainly update this thread if I figure anything out.

  • Verified answer
    RCCHULUOTA Profile Picture
    on at

    OK, so I think I might have found a fix.  It seems that updating the DEX_ROW_TS value for a record in the IV00107 table (Price list options table) triggers the connector to see the records as updated.  I've run the following:

    update IV00107

    set DEX_ROW_TS = GETUTCDATE()

    where PRCLEVEL = 'CITY/CO'

    to attempt to have the connector sync over our price list named 'CITY/CO' which previously only had 90 or so of the 2214 lines in it.  Right now the connector has detected 2214 changes and is syncing them so far without issue.  If this continues to work for this and the 10 other price lists, it'll be a good fix as new items and individual changes seem to be picked up on right away during normal use.  I'll keep this thread updated.

  • RCCHULUOTA Profile Picture
    on at

    After running the above script for each price level and letting the connector sync the changes over before running it for the next price level has fixed the issue and all of the price lists now contain the correct number of items.  There still seems to be something broken in the connector though as I just removed a few price list items using GP's price list utilities and none of those changes were found or synced over.  Oh well, that's a problem for another day.

  • Michael Siegel Profile Picture
    25 on at

    What you have executed is a workaround.  What I is actually happening is that the web service sends its first request to econnect using a query that returns the first 1000 records in your item price lists where the DEX_ROW_TS > 1/1/1900.  It then uses the item number > , currency = , price level =, and DEX_ROW_TS>1/1/1900 from the last item in the first set of results to generate the next results and so on.  The problem is that writing a condition on price level curtails the integration of multiple price lists as we have both experienced.  I am working with Microsoft on a solution.  If I have any luck, I'll post a solution here.

  • RCCHULUOTA Profile Picture
    on at

    Thanks for the info on the actual problem.  That makes sense.  Please do post any additional info you get about this!

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans