Jump to content

thielnthiel

Newbies
  • Posts

    4
  • Joined

  • Last visited

thielnthiel's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Hello Everyone! Been using the plugin for a while now and recently just had to update the FMPA client version to 18, meaning the bridge file needs to be utilized to have them talk. Here's some detail: Windows 2012 Server Quickbooks Enterprise Desktop 2019 FileMaker Pro Advanced 18 Fmbooks connector 12.0.0.0.5 Users accessing FM + QB via RemoteApp What we did: Removed all previous plugin files from both Program Files and each active User's AppData Cleared Certificates from Quickbooks and from User>AppData>Local>PCINC>FMBCONNECT Installed new plugin version. Selected "For Everyone on this computer". Kept the default location as recommended, that location was User[me]>AppData>Local>FileMaker>FileMaker Pro Advanced 18>Extensions Registered Plugin Signed AdminUser on. No splashscreen for plugin. Confirmed plugin was not installed. Copied plugin file to Program Files > FileMaker > Extensions Confirmed that installed the plugin file for AdminUser Registered plugin. Established Initial connection to QB company file. Selected Always allow access, login as specific User [me] Success! Was able to connect through Remote Desktop and via RemoteApp. Repeated these steps with users: via RemoteApp, Registered the plugin. Try BeginSession Error throws: Bridge File Not Found. Log into the remote desktop as that User, and clicked Setup on the Install QB Bridge File. Was only give the option to Repair or Remove the bridge. Clicked Repair. Success! Was able to begin session in both the Remote Desktop and then via RemoteApp [after exiting both apps on remote desktop and signing out]. Next Day Users Opens QB, then opens FileMaker. BeginSession again throws error "Bridge File Not Found" User logs into remote desktop and tries to connect there. Throws error "Bridge File Not Found". User Clicked Setup on Install QB Bridge File. Again selected the option to Repair the bridge file. Success.... but we can't have to do that everyday. The user who initially installed the plugin [me] and the AdminUser who established the first connection have no trouble with the bridge file. I'm thinking whether there are specific locations on where we need to install the plugin and/or bridge when using the installer? Thanks All for your help! Nixon
  2. I'm an idiot! you guys were both correct, they are fields from Estimates Thank you for the help!!
  3. Geoffrey, I'm pretty sure the fields were defined in QB itself. Yes with the PCQB_SGETXML function. I didn't think about the % symbol coming back encoded, which it probably would however I don't see the fields anywhere at all in the XML. here is the line item in QB --> and here is the XML for the invoice, with the above line being the last LineItem in the XML <InvoiceRet> <TxnID>111A21-1525273534</TxnID> <TimeCreated>2018-05-02T10:05:34-06:00</TimeCreated> <TimeModified>2018-05-29T11:24:08-06:00</TimeModified> <EditSequence>1525273534</EditSequence> <TxnNumber>101457</TxnNumber> <CustomerRef> <ListID>80001DA5-1506523615</ListID> <FullName></FullName> </CustomerRef> <ARAccountRef> <ListID>3E0000-884317953</ListID> <FullName>Accounts Receivable</FullName> </ARAccountRef> <TemplateRef> <ListID>E0000-1117116752</ListID> <FullName>D) Other - Progress Invoice</FullName> </TemplateRef> <TxnDate>2018-04-30</TxnDate> <RefNumber>10883</RefNumber> <BillAddress> <Addr1>/Addr1> <Addr2></Addr2> <City></City> <State>TX</State> <PostalCode>75234</PostalCode> </BillAddress> <BillAddressBlock> <Addr1></Addr1> <Addr2></Addr2> <Addr3></Addr3> </BillAddressBlock> <IsPending>false</IsPending> <IsFinanceCharge>false</IsFinanceCharge> <DueDate>2018-04-30</DueDate> <ShipDate>2018-04-30</ShipDate> <Subtotal>15885.00</Subtotal> <ItemSalesTaxRef> <ListID>1D0000-918242596</ListID> <FullName>SalesTax</FullName> </ItemSalesTaxRef> <SalesTaxPercentage>8.25</SalesTaxPercentage> <SalesTaxTotal>0.00</SalesTaxTotal> <AppliedAmount>-15885.00</AppliedAmount> <BalanceRemaining>0.00</BalanceRemaining> <IsPaid>true</IsPaid> <IsToBePrinted>false</IsToBePrinted> <IsToBeEmailed>false</IsToBeEmailed> <CustomerSalesTaxCodeRef> <ListID>20000-1033839081</ListID> <FullName>Non</FullName> </CustomerSalesTaxCodeRef> <InvoiceLineRet> <TxnLineID>111A23-1525273534</TxnLineID> <Desc>Professional Architectural Interior Design Services provided for Change Order #4 as set forth in agreement dated March 5, 2018 as follows:</Desc> </InvoiceLineRet> <InvoiceLineRet> <TxnLineID>111A24-1525273534</TxnLineID> </InvoiceLineRet> <InvoiceLineRet> <TxnLineID>111A25-1525273534</TxnLineID> <ItemRef> <ListID>800000E0-1489084293</ListID> <FullName>BA</FullName> </ItemRef> <Desc>Bid Administration &amp; Construction Administration</Desc> <Quantity>0.6</Quantity> <Rate>26475.00</Rate> <ClassRef> <ListID>8000000A-1359658740</ListID> <FullName>OP</FullName> </ClassRef> <Amount>15885.00</Amount> <SalesTaxCodeRef> <ListID>20000-1033839081</ListID> <FullName>Non</FullName> </SalesTaxCodeRef> </InvoiceLineRet> </InvoiceRet> Thanks for the help!
  4. Hi there, I am trying to query custom fields in invoice line items and am having trouble getting the LineItem DataExt object in the response. I pass OwnerID as 0 in the InvoiceQuery Request but i don't get any DataExt objects in the response at all (when i check the XML Response text). Is there something else i need to add to the Request? The fields i'm trying to get are "% Complete" and "% This Billing" -- custom Line Item fields See below script! Set Variable [ $QBListID; Value:PROJECTS_MainMenu::QBListID ] Set Variable [ $result; Value:PCQB_RqNew( "InvoiceQuery"; "" ) ] Set Variable [ $result; Value:PCQB_RqAddFieldWithValue( "EntityFilter:ListID" ; $QBListID )] Set Variable [ $result; Value:PCQB_RqAddFieldWithValue( "IncludeLineItems" ; True )] // Set Variable [ $result; Value:PCQB_RqAddFieldWithValue( "IncludeRetElement" ; "DataExtRet")] Set Variable [ $result; Value:PCQB_RqAddFieldWithValue( "OwnerID" ; "0" )] Set Field [ Utility::g.QBResult; PCQB_RqExecute ] Perform Script [ “Check for FMConnector Errors (Halt)” ] Set Variable [ $result; Value:PCQB_RsOpenFirstRecord ] Set Variable [ $i; Value:0 ] Loop Exit Loop If [ $Result= "!!ERROR!!" or $Result= "End" or $Result= "?" ] Set Variable [ $InvoiceDate; Value:PCQB_RsGetFirstFieldValue( "Detail:TxnDate" )] Set Variable [ $json; Value:JSONSetElement ( $json; "Invoices["& $i &"]Date" ; $InvoiceDate; JSONString ) ] Set Variable [ $result; Value:PCQB_RsOpenFirstRelatedRecord( "InvoiceLineRet" ) ] Set Variable [ $z; Value:0 ] Loop Exit Loop If [ $Result= "!!ERROR!!" or $Result= "End" or $Result= "?" ] Set Variable [ $amount; Value:PCQB_RsGetFirstFieldValue( "Amount" )] Set Variable [ $json; Value:JSONSetElement ( $json; "Invoices[" &$i& "]Line[" &$z& "]Amount"; $amount ; JSONNumber ) ] Set Variable [ $result; Value:PCQB_RsOpenFirstRelatedRecord( "DataExtRet" ) ] Loop Exit Loop If [ $Result= "!!ERROR!!" or $Result= "End" or $Result= "?" ] Set Variable [ $pField; Value:PCQB_RsGetFirstFieldValue( "DataExtName" )] If [ PatternCount ( $pField ; "% COMPLETE") ] Set Variable [ $pComplete; Value:PCQB_RsGetFirstFieldValue( "DataExtValue" )] Set Variable [ $json; Value:JSONSetElement ( $json; "Invoices["& $i &"]Line[" & $z &"]PercentageComplete" ; $pComplete; JSONString ) ] Else If [ PatternCount ( $pField ; "% This Billing" ) ] Set Variable [ $billingThis; Value:PCQB_RsGetFirstFieldValue( "DataExtValue" )] Set Variable [ $json; Value:JSONSetElement ( $json; "Invoices["& $i &"]Line[" & $z &"]PercentageBilling" ; $billingThis; JSONString) ] End If Set Variable [ $result; Value:PCQB_RsOpenNextRelatedRecord ] End Loop Set Variable [ $result; Value:PCQB_RsCloseRelatedRecord ] Set Variable [ $z; Value:$z + 1 ] Set Variable [ $result; Value:PCQB_RsOpenNextRelatedRecord ] End Loop Set Variable [ $result; Value:PCQB_RsCloseRelatedRecord ] Set Variable [ $i; Value:$i + 1 ] Set Variable [ $result; Value:PCQB_RsOpenNextRecord ] End Loop
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.