You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, thank you for developing this great module. It is very convenient and meets all our requirements. Recently, I deployed an app with strict permissions for the user executing the app and noticed that Zeep, by default, uses an SQLite cache backend. This caused the app to fail for us because the user had no permissions to write outside of the application directory. After a closer inspection, I noticed the NetSuite class allows for a cache parameter to be passed via soap_api_options. I'm sharing this so others with a similar problem may find it helpful.
An alternative approach would be to specify the path for the SQLite backend as shown in their documentation.
Another interesting issue we ran into was trying to download files larger than 10MB using the SOAP API. By default, Zeep's settings prevent that (response is truncated) unless we set xml_huge_tree to True, like so:
Hello,
Firstly, thank you for developing this great module. It is very convenient and meets all our requirements. Recently, I deployed an app with strict permissions for the user executing the app and noticed that Zeep, by default, uses an SQLite cache backend. This caused the app to fail for us because the user had no permissions to write outside of the application directory. After a closer inspection, I noticed the NetSuite class allows for a cache parameter to be passed via
soap_api_options
. I'm sharing this so others with a similar problem may find it helpful.An alternative approach would be to specify the path for the SQLite backend as shown in their documentation.
Another interesting issue we ran into was trying to download files larger than 10MB using the SOAP API. By default, Zeep's settings prevent that (response is truncated) unless we set
xml_huge_tree
toTrue
, like so:Hope this helps. Thanks again!
The text was updated successfully, but these errors were encountered: