Added DataDocument for creating a view of required NetSuite Fields #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
###This is functioning properly except for fields that are required to be queried twice:
##Limitations:
ContactMech.infoString
field needs to be fetched for both SHIPPING_EMAIL and BILLING_EMAIL purposes.SHIPPING_EMAIL
orBILLING_EMAIL
and puts it in the aliased fields.in
operator for now to fetch eligible records)in
operator is used then suppose if one of the contactMechPurposeTypeId has no corresponding record then in that case it fetches all the contactMechs from the entity and prints them in the document (SHIPPING_EMAIL is null in my case)