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)

How we fetch DEX_ROW_ID in "Payables_History_Transaction" through eConnect_Requester ?

(0) ShareShare
ReportReport
Posted on by 617

Hi All, 

Anyone can assist us we want to retrieve data through eConnect, we successfully fetch the data but DEX_ROW_ID column doesn't exist and we want DEX_ROW_ID column also.

For your information we pass the following parameters, please let us know how we retrieve the DEX_ROW_ID column also. 

myeConnectOut.ACTION = 1;
myeConnectOut.DOCTYPE = "Payables_History_Transaction";
myeConnectOut.OUTPUTTYPE = 2;
myeConnectOut.INDEX3FROM = "";
myeConnectOut.INDEX3TO = "";
myeConnectOut.FORLIST = 1;
myeConnectOut.ROWCOUNT = 0;

Thanks & Regards, 

Govind Devda

*This post is locked for comments

I have the same question (0)
  • Tim Wappat Profile Picture
    5,715 on at

    DEX_ROW_ID is not included as you shouldn't need it.

    See my post on not using DEX_ROW_ID in integrations or relying on it as a unique identifier, in summary it is not guaranteed  to stay the same relative to the record, especially during upgrades.

    timwappat.info/.../DEX_ROW_ID-Dynamics-GP-column-integrations-or-Customisation

    If you look at

    select * from  [dbo].[eConnect_Out_Setup]

    Where

    doctype='Payables_History_Transaction'

    you will see that DEX_ROW_ID is not included in the output columns (DATAxx), you could add it to the first empty DATA column in that table.

    Remember to inclurement the data count column (see : timwappat.info/.../eConnect-Customer-Requester-Document-No-ShipToName-field )

    Also may help: timwappat.info/.../eConnect-Requester-Documents-sourced-from-Custom-table-or-Views

    Also use your internet search engine and look for “extend eConnect requester” to find the MS documentation relating to this area.

    Personally I would create a copy of the requester as a custom requester document and add the extra to that so the original stays intact, in case other products you add in the future rely on it being vanilla.

    Remember that changing requester definitions requires you to back them up and possibly restore them after upgrades or re-installs of eConnect, so it may be wise to set a SQL job up to monitor or keep these in place.

    Tim.

  • Suggested answer
    MG-16101311-0 Profile Picture
    26,225 on at

    Using the DEX_ROW_ID to do any type of operation is extremely risky from a data integrity perspective. See my article dynamicsgpblogster.blogspot.com/.../dexrowid-column.html. If you insist, you will have to create your own stored procedure or pass-through SQL to retrieve the DEX_ROW_ID based on the key of the table you are trying to pull the info from.

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 May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans