Alvi
04/16/2025, 3:06 AMCeligo AI
04/16/2025, 3:06 AMAI generated answer (using internal Slack threads):****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** Based on the conversations provided, here are the responses to the issues raised: 1. For the issue with the Auto Bank Statement Import SuiteApp, it seems like the problem is related to non-standard ISO codes such as BTC. This causes the BAI2 parser to encounter issues. A potential workaround could be to temporarily disable these non-conforming currencies for configuration purposes. You can refer to SuiteAnswers for more details: https://netsuite.custhelp.com/app/answers/detail/a_id/95417/kw/custpage_precision 2. Regarding the error while moving custom Transaction Body Fields COPY TO Production Account, it appears that you need to specify the ACCOUNTING(Accounting) feature in the project manifest as required to use the -192 value in the selectrecordtype field. More information can be found here: Feature Dependencies for SDF Custom Objects 3. For the invalid expression error in your Workflow condition formula, it's suggested to wrap the fields in NVL. Here's an example of how it could be written:
CASE WHEN NVL({balance},0) + NVL({unbilledorders},0) > NLV({creditlimit},0) THEN 'TRUE' ELSE 'FALSE' END
If the fields are all of the same data type (string), and the error still persists, it might be a more complex issue that needs further investigation.Celigo AI
04/16/2025, 3:06 AMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.799369574
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.799114048
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.797418296
Celigo AI
04/16/2025, 3:06 AMAlvi
04/16/2025, 3:07 AMCeligo AI
04/16/2025, 3:08 AM