Search results by user ID 23046

Re: Formatting a date in an email

botanica — Thu, 14 May 2020 17:13:07 GMT

Hi Inder -

Yes, thanks to your team and Tiffany I've got it working.

One of my many issues was that at the bottom of my character function, I was not reassigning the result back into resultEmailBodyMerge.

For anyone else that comes across this thread, here is my complete solution to formatting dates in my email template.

I added three actions before the Show Email and Send Email actions in my Email button. And in my email template I use the string resultTxnDate.

Formatting a date in an email

botanica — Wed, 13 May 2020 20:04:52 GMT

Hello -

I would like to format the TxnDate of a sales order in an email template.

I've added two functions to my email button on my sales order screen.

A date function to format TxnDate and store in FTxnDate: https://imgur.com/XDXLVNY.png

And a character function to replace TxnDate within resultEmailBodyMerge with FTxnDate: https://imgur.com/mEXCjew.png

Do I then add the FTxnDate field to my email template? Can anyone give me any hints as to where I'm going wrong, please?

Re: Invalid XML returned from soap response when retrieving InvoiceLine table

botanica — Wed, 25 Sep 2019 16:13:30 GMT

Got it, thank you! I didn't notice the lxml limit.

Re: Invalid XML returned from soap response when retrieving InvoiceLine table

botanica — Mon, 23 Sep 2019 21:56:00 GMT

Thanks for the quick reply.

Yeah we have a few different Method accounts with which we do a lot of the same stuff against the API (like pulling invoices) and only one of our accounts is having this issue. It really seems to be some sort of limit being reached (albeit perhaps no longer an issue with the xml_huge_tree setting in zeep enabled). I am retrieving all invoices and all invoice lines in order to build a data set using python/pandas that I then use to populate a dashboard. Is it not recommended to retrieve all invoice lines at once?

Invalid XML returned from soap response when retrieving InvoiceLine table

botanica — Mon, 23 Sep 2019 18:46:48 GMT

I'm attempting to pull the InvoiceLine table via a python script that's been working for months but all of a sudden is having issues.

The zeep client (or underlying lxml pkg) is having issues parsing the soap response:

Traceback (most recent call last):

File "/home/user/envs/sales/lib/python3.6/site-packages/zeep/wsdl/bindings/soap.py", line 170, in process_reply
doc = parse_xml(content, self.transport, settings=client.settings)
File "/home/user/envs/sales/lib/python3.6/site-packages/zeep/loader.py", line 54, in parse_xml
content=content
zeep.exceptions.XMLSyntaxError: Invalid XML content received (xmlSAX2Characters: huge text node, line 321734, column 43)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/home/user/envs/sales/lib/python3.6/site-packages/zeep/proxy.py", line 42, in __call__
self._op_name, args, kwargs)
File "/home/user/envs/sales/lib/python3.6/site-packages/zeep/wsdl/bindings/soap.py", line 132, in send
return self.process_reply(client, operation_obj, response)
File "/home/user/envs/sales/lib/python3.6/site-packages/zeep/wsdl/bindings/soap.py", line 176, in process_reply
content=response.content)
zeep.exceptions.TransportError: Server returned response (200) with invalid XML: Invalid XML content received (xmlSAX2Characters: huge text node, line 321734, column 43).

I'm requesting the following fields from the InvoiceLine table:

'Item', 'Amount', 'Class', 'Desc', 'InvoiceAmount', 'LotNumber', 'Other1', 'Quantity', 'Rate', 'Other2', 'TotalAmount', 'InvoiceRecordID', 'RecordID', 'TxnLineID'

Strange this is if I exclude any of the above fields then the reponse comes back fine. Is there just too much data being returned?

EDIT:

I enabled the xml_huge_tree setting in the zeep client and am no longer having this issue.

>xml_huge_tree – disable lxml/libxml2 security restrictions and support very deep trees and very long text content

I'm still not sure what is happening here, if anyone can shed some light on it would be much appreciated.

Re: Service Unavailable 503

botanica — Wed, 20 Feb 2019 16:06:05 GMT

Thank you for the update, Paul. We're excited to get started with Method.

Re: Service Unavailable 503

botanica — Wed, 20 Feb 2019 02:51:36 GMT

dknoben - negative, my company is still working on transitioning to QB and Method so I wasn't actually impacted by the outage so I didn't do much follow-up on it.

Re: Service Unavailable 503

botanica — Mon, 18 Feb 2019 18:16:24 GMT

Blake - I was getting the same thing Sunday afternoon for several hours until it cleared up late evening.