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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Setting Vendor Status ...
Microsoft Dynamics GP (Archived)

Setting Vendor Status using eConnect

(0) ShareShare
ReportReport
Posted on by Drewguy007 50

I am developing an integration between an existing application and Dynamics GP 2013 using eConnect.  My application is supposed to create a new vendor with a status of 'temporary' and then create a payable transaction for the newly created vendor.  Everything is working perfectly except for setting the vendor status to 'temporary'.  

In the taUpdateCreateVendorRcd schema, I am setting the VENDSTTS value to 3 and the UpdateIfExists value to 2.  That doesn't work.  I also tried making a call specifically to CreateEntity with a PMVendorMasterType to create the vendor, then update the status to 'temporary' during the transaction creation.  That doesn't work.  I just can't get the status to change from 'active' to 'temporary'.

One other curious thing that I noticed is that the VENDSTTS node does not seem to be included in the result XML that I get back from the call to CreateTransactionEntity.  

Has anyone else run across this issue and found a way to get it to work?

Thanks!

*This post is locked for comments

I have the same question (0)
  • Verified answer
    steveendow Profile Picture
    steveendow 2,281 on at

    Hi,

    When you set VENDSTTS, are you also setting the VENDSTTSSpecified property to true?

    I don't know what the historical explanation is, but some eConnect properties have a "Specified" property that you must set to true for them to be serialized.  Apparently these are called "Serialization Flags".

    The older eConnect help files used to list these fields at the bottom of each schema, but starting with GP 2010, the help no longer lists them, so you just have to know to look for them in Intellisense when assigning the property values.

    Let me know if adding the VENDSTTSSpecified = true solves your issue.  If not, we can look into other possible causes.

  • Drewguy007 Profile Picture
    Drewguy007 50 on at

    Thanks for the answer Steve.  I did have to pay attention to the contents of Intellisense to see that the object does have a VENDSTTSSpecified property.  After setting that to true, the property was serialized, and GP was updated appropriately.  

    Big time saver and something I will definitely keep in mind in the future.

    Andrew

  • steveendow Profile Picture
    steveendow 2,281 on at

    Hi Andrew,

    Glad that solved your issue.

    I've written a blog post discussing the now-undocumented serialization flags.

    dynamicsgpland.blogspot.com/.../undocument-econnect-2010-and-2013.html

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans