DynDeveloper.com

This is not ground breaking code, it's kind of mundane. But it took me 3 hours to get it all working; I'm going to blog it so I don't have to do it again.

This article shows a SQL script and a DOS batch file that can be used to backup an instance of SQL Express, and then to delete files older than x days.

This article will be the overview for the process of installing Service Based Architecture for Dynamics GP. There are several steps, we'll break them up to make it easier to understand. For an overview of all the steps, look here

This article will walk you through creating a Self Signed Certificate in IIS 8. This certificate will be necessary to install Dynamics GP Web Components

Installing Service Based Architecture for Dynamics GP is a series of steps that need to be coordinated. Be sure that you're using our guide located here

When I populate dropdownlists, I frequently want to add a new row at the top. I've figured out that you can easily add one at the bottom with DataTable.Rows.Add(), but that's... not elegant. This article is just a few lines of code that shows how to add one at the top.

Why bother blogging such a simple piece of code?

RAD.

I want to code quickly and efficiently and I can do that best if I have all the code samples that I needs at my fingertips instead of having to wade through endless blog entries. (some of which are innacurate)

Are you using the menus? Any subjects we can add? Tutorials

I am trying to create a Project Costing Report using Project Accounting tables.  It appears I am missing price changes (between the receiving of the material and the invoice), project add-ons, etc...  Looking at the combined history table, it looks like table "PA01001" has this information.   

My question is regarding the linking to this table.  Have any of you used this table and what field are you joining to? 

Thank you,

Regards,

Tom

Error: Duplicate Order

Hi, I'm trying to join cm20200 with gl20000. I need to see which checkbook entries are missing from the GL cash account. I can get close, but I keep running into non unique fields to join on. I've used case statements to try and cut the data differently. They help, but generally lead to a one to many. Any suggestions on how to trace an entry from cm20200 to gl20000 that will cover all the different types of cm20200 possibilities?

tthanks!

My customer wants all the quantities we import to go into QTYTBAOR so they do not affect inventory.  They adjust this field at the time they process & ship.

I tried setting QTYTBAOR = to the quantity ordered but I’m getting the eConnect error below.  I was able to get the order in when I set DEFPRICING = 1 but it no longer used the correct price level (PRCLEVEL) and it seemed to think there were 2 items instead of 1.  I tried removing the QUANITY field but that’s mandatory.  Can you help me understand what combination of values I need to set to make this work?  Thank you!

Error Number = 299  Stored Procedure= taSopLineIvcInsert  Error Description = Unit Price calculation does not match out to Extended price

Node Identifier Parameters: taSopLineIvcInsert

SOPNUMBE = ORD0046790

SOPTYPE = 2

LNITMSEQ = 16384

Related Error Code Parameters for Node : taSopLineIvcInsert

SOPTYPE = 2

QUANTITY = 1.00

UNITPRCE = 15.17

MRKDNAMT = Note: This parameter was not passed in, no value for the parameter will be returned.

XTNDPRCE = 15.17

<taSopLineIvcInsert>

  <SOPTYPE>2</SOPTYPE>

  <CUSTNMBR>XXXX</CUSTNMBR>

  <DOCDATE>03/26/2015</DOCDATE>

  <ITEMNMBR>XXXX</ITEMNMBR>

  <PRCLEVEL>XXXX</PRCLEVEL>

  <UNITPRCE>15.17</UNITPRCE>

  <XTNDPRCE>15.17</XTNDPRCE>

  <QUANTITY>1.00</QUANTITY>

  <QTYTBAOR>1.00</QTYTBAOR>

  <LNITMSEQ>16384</LNITMSEQ>

  <DOCID>STDORD</DOCID>

  <PRSTADCD>XXXX</PRSTADCD>

  <ReqShipDate>03/13/2015</ReqShipDate>

  <QTYFULFI>0</QTYFULFI>

  <QTYFULFISpecified>True</QTYFULFISpecified>

  <UOFM>Case</UOFM>

  <USRDEFND3>00003</USRDEFND3>

  <SOPNUMBE>ORD0046790</SOPNUMBE>

</taSopLineIvcInsert>

I am seeing a scenario where we are getting "001" appended to the end of the document number.

Example:

Cm12345001 for a Sales Entry (BCHSOURC)

Then we have a RM_Sales (BCHSOURC) with a document number Cm12345.

I google this and found some information that seemed to indicate that this is by design if there are 2 documents with the same doc number. I did not find anything in the GP help file.

Can anyone confirm that this is by design, or is there something else possibly incorrect?

We are using GP 2010