DynDeveloper.com

Many of us have been struggling with failing RDP connections since an O/S update went out from Microsoft on Tuesday (5/8/18)

The answer to the connection issue is to patch all the computers involved and it should be fine. But often server owners need to control how updates are applied for a variety of very good reasons... so we have a problem. 

I found a solution that worked for me and I'm posting it below so I don't lose it...

Please understand that this approach is not best practice and will allow the security vulnerability to continue. But I don't have a choice, I need to get to work.

I have a user who wishes to correct the labor cost on an entry for April.

The manufacturing order is in a closed state. What is the proper method to make this correction?

Is there a way to re-open the MO and make the correction?

Thank you,

Will

How to extract data for Open Item Receivable and Open Item Payable for a particular date say Dec 31.

Error: DOCID does not exist for document type

I am deploying a chunk file to a dev GP2016 installation. The chunk extracts fine but I do not see the changes on the screen. This used to work fine so chunk creation macro is fine.

But suddenly the changes do not appear to show. Has anyone seen this issue and what is the solution. Someone suggested to do a fresh install of GP but that seems excessive to me. Please advise.

Hi 

I am trying to edit order through econenct. When I change the tax value or freight amount for first time it gets updated. But second time it throws error 

Setting the taxes through header. The salesHdr.USINGHEADERLEVELTAXES is set to 1;

Error Number = 8329  Stored Procedure= taSopHdrRecalc  Error Description = Tax table detail does not equal the tax amount - manual tax changes are not supported on Updates
Node Identifier Parameters: taSopHdrRecalc
SOPNUMBE = EDI0001300435
SOPTYPE = 2

I have attached xml for refrence .

thanks 

Priya

Good evening,

  You can recommend to me a user friendly tool for customize Financial Report for GP 2015.

Sincerely,

  Mr. García

The attached xml is an example found on this site, as would be the structure of this xml for a return, transaction type = 4, considering that the merchandise is returned to available.

<eConnect xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <SOPTransactionType>
    <eConnectProcessInfo xsi:nil="true"/>
    <taSopLineIvcInsert_Items>
      <taSopLineIvcInsert>
        <SOPTYPE>3</SOPTYPE>
        <ITEMNMBR>COMPBOOK</ITEMNMBR>
        <QUANTITY>2</QUANTITY>
        <CUSTNMBR>AARONFIT0001</CUSTNMBR>
        <DOCDATE>4/1/2010</DOCDATE>
        <LOCNCODE>WAREHOUSE</LOCNCODE>
        <DEFPRICING>1</DEFPRICING>
      </taSopLineIvcInsert>
    </taSopLineIvcInsert_Items>
    <taSopHdrIvcInsert>
      <SOPTYPE>3</SOPTYPE>
      <DOCID>STDINV</DOCID>
      <CUSTNMBR>AARONFIT0001</CUSTNMBR>
      <BACHNUMB>TESTBATCH</BACHNUMB>
      <DOCDATE>02/04/2011</DOCDATE>
      <LOCNCODE>WAREHOUSE</LOCNCODE>
      <DEFPRICING>1</DEFPRICING>
      <CREATETAXES>1</CREATETAXES>
      <DEFTAXSCHDS>1</DEFTAXSCHDS>
    </taSopHdrIvcInsert>  </SOPTransactionType>
</eConnect>

I'm able to set sales order item fulfilled qty and lot/serials for lines but not for kit components.  
Seems like the only difference is the componentsequencnumber in the SalesComponentKey.  

salesdoc.Lines[j].Components[k].QuantityFulfilled.Value = salesdoc.Lines[j].Components[k].QuantityFulfilled.Value + CLine.DeltaQty;

Then for lots:

var lots = new List<SalesComponentLot>();
for (int i = 0; i < ShipItem.Distributions.Length; i++)
{
     SalesComponentLot lot = new SalesComponentLot();
     lot.LotNumber = ShipItem.Distributions[i].LotSerial;
     lot.Quantity = new Quantity { Value = ShipItem.Distributions[i].Quantity };
     lot.Bin = null;
     lot.Key = new SalesComponentLotKey();
     lot.Key.QuantityType = QuantityType.OnHand;
     lot.Key.SequenceNumber = (i + 1);
     lot.Key.SalesComponentKey = new SalesComponentKey();
     lot.Key.SalesComponentKey.ComponentSequenceNumber = salesdoc.Lines[j].Components[k].Key.ComponentSequenceNumber;
     lot.Key.SalesComponentKey.SalesLineKey = new SalesLineKey();
     lot.Key.SalesComponentKey.SalesLineKey.LineSequenceNumber = salesdoc.Lines[j].Components[k].Key.SalesLineKey.LineSequenceNumber;
     lot.Key.SalesComponentKey.SalesLineKey.SalesDocumentKey = new SalesDocumentKey();
     lot.Key.SalesComponentKey.SalesLineKey.SalesDocumentKey.Id = salesdoc.Lines[j].Components[k].Key.SalesLineKey.SalesDocumentKey.Id;               
     lots.Add(lot);
}
salesdoc.Lines[j].Components[k].Lots = lots.ToArray();

Full error from event viewer is

Action: Create Current User Name: V-TECH\Judy Input parameters: Exception type: Microsoft.Dynamics.GP.eConnect.eConnectException Exception message: Sql procedure error codes returned: Error Number = 115 Stored Procedure= taSopLineIvcInsert Error Description = Unable to insert the component record Node Identifier Parameters: taSopLineIvcInsert SOPNUMBE = TST0034 SOPTYPE = 2 LNITMSEQ = 16384 Error Number = 3462 Stored Procedure= taSopLineIvcInsertComponent Error Description = if AUTOALLOCATELOT = 1 or 2, the taSopLotAuto node must be called with a DOCID that fulfills or QTYFULFI > 0 Node Identifier Parameters: taSopLineIvcInsertComponent SOPNUMBE = TST0034 SOPTYPE = 2 ITEMNMBR = TEST03 LNITMSEQ = 16384 Related Error Code Parameters for Node : taSopLineIvcInsertComponent AUTOALLOCATELOT = 1 QTYFULFI = 1.00000

 Stack Trace: at Microsoft.Dynamics.GP.eConnect.EntityMessageProcessor.ExecuteSqlCommands(XElement transactionNode, EntityMessage message) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.ProcessMessageImport(EntityMessage message) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.EntityImportImplementation(String connectionString, String sXML, Boolean isTransaction) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateEntity(String connectionString, String sXML) Exception type: Microsoft.Dynamics.GP.eConnect.eConnectException Exception message: Error Number = 115 Stored Procedure taSopLineIvcInsert Error Description = Unable to insert the component record Error Number = 3462 Stored Procedure taSopLineIvcInsertComponent Error Description = if AUTOALLOCATELOT = 1 or 2, the taSopLotAuto node must be called with a DOCID that fulfills or QTYFULFI > 0 Stack Trace: