ANSWERED - eConnect: The VNDCHKNM field is getting set to the VENDNAME field

Search the GP Tables

Search by TABLE NAME

Search by FIELD NAME

These are our SOP scripts. All of our scripts for Dynamics GP can be found here

	SOP Scripts
	eConnect
	taSopDeleteDocumentWrapper
	taSopLineDeleteWrapper
	taSOPLineIvcInsert Wrapper
	taSopLineIvcInsertComponent
	taSOPLotAuto - complete procedure
	Functions
	ddf_Address
	ddf_AllHoldsOnASOPDoc
	General
	Getting Email addresses from Dynamics GP
	Move a SOP transaction from open to history
	Posting Sequences
	SOP40200 'Allow' fields query
	sopGetIDNumber
	sopTrxDeleteWork
	Unvoid a SOP document
	Stored Procedures
	dd_SOP10102_UPD
	dd_SOPGetNextDocNumber/ sopGetIDNumber.
	dd_SOPPayment_INS
	dd_SOPRound - Round a SOP Multicurrency document to two decimal places
	dd_SOPTotal
	dd_SOPTotalTaxes
	dd_taSopVoidDocumentWrapper

NaomiP 8/26/2009 4:11:12 PM

eConnect: The VNDCHKNM field is getting set to the VENDNAME field

In GP9:

I'm running taUpdateCreateVendorRcd, and the client is asking if I can not update the Check Name field if the address already exists. So, I opened taUpdateCreateVendorRcdPre and wrote this code:

Version: Unknown or N/A

Section: eConnect

Table Definition Quick Links

All Tables

SOP Tables

RM Tables

GL Tables

POP Tables

HR Tables

PM Tables

UPR Tables

IV Tables

Olympic Tables

DynDeveloper.com

eConnect: The VNDCHKNM field is getting set to the VENDNAME field