Versions Compared
Version | Old Version 1 | New Version Current |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Table of Contents
Table of Contents | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Version |
| ||||||
Available as of Date |
Technical Changes
Enhancement
Then user can now select locations from other subsidiaries in the Vendor Record: FlowAP Default Location field {custentity_sta_flowap_defaultloc}.
Bug Fix
FlowAP Documents with empty Transaction type will be converted as Vendor Bill. Vendor Bill is the default transaction type.
A fix was implemented so that FlowAP Lookup and Parsing Functions will consider XML elements with only whitespaces as empty / null.
The following Electronic Bank Detail creation and primary type rules have been implemented.
XML: Electronic Bank Detail | NetSuite Vendor: Electronic Bank Detail | Expected Result |
---|---|---|
Single electronic bank detail | Empty | Create the EBD set as primary |
Single electronic bank detail | Not empty, and the bank detail matches the existing record. | Set the matching EBD as primary |
Single electronic bank detail | Not empty, and the bank detail does not match the existing record. | Create the EBD set as primary |
Multiple electronic bank detail | Empty | Create all the EBDs in the XML. Set the first created EBD as primary and the remaining EBDs as secondary. |
Multiple electronic bank detail | Not empty, and the bank detail does not match the existing record. | Create all the EBDs in the XML. Set the first created EBD as primary and the remaining EBDs as secondary. |
Multiple electronic bank detail | Not empty, and there is one matching bank detail record between the XML and the vendor record. | Create all the non-matching EBDs in the XML. Set the matching EBD as primary. The rest of the EBDs as secondary. |
Multiple electronic bank detail | Not empty, and there is more than one matching bank detail record between the XML and the vendor record. | Create all the non-matching EBDs in the XML. Set the first matching EBD as primary. The rest of the EBDs as secondary. |
Multiple electronic bank detail | Not empty, and all bank detail record between the XML and the vendor record matches. | Set the first matching EBD as primary. |
FlowAP Documents with empty Transaction type will be converted as Vendor Bill. Vendor Bill is the default transaction type.
. |
Required Actions for the End user
N/A
Send an email to support@staria.com for questions or concerns regarding this topic.