Data Export feature Support

V5 Question
1

So have encountered a few issues with the Export Supported Features and need some guidance on what can be done in an Export.

Here is what I have discovered so far:

DataExportSupport.JPG1168×294 58.1 KB

Questions:

  1. Its not marked but I assume the use of “@” parameters is not supported?
  2. How can we get line breaks in the export WITHIN a REPORT tag?
  3. Any ideas on how I can get around the Parser breaking when using a {CALL:x “REPORT Tag”} command sequence?

Thanks.

[EDIT:]
Ok place a Table into the mix and it fired up!

DataExportSupportTable.JPG1346×332 64.2 KB

So any idea why my {CALL:x} is being truncated down :disappointed:

[EDIT 2:]
Ok it is being truncated down due to custom field EC.Orders which is a widestr - contains special characters which break the Custom Field Parser!

Now looking at using another “marker” field inside the Widestr :tired_face:

SOLUTION:
JScript to the rescue! Recursive call of Script got over the line by supplyng special character after the Custom Field Conversion :smile:

DataExportSupportTableSolved.JPG1071×394 82.6 KB

@emre I probably can fix the {0} becoming "{0}" using yet another bit of Script but thought you should know
the {CALL:x} Parser can break if quotes are used above. Maybe you have a better construction of the syntax above?

AND we are done here!
Modified the Script to RETURN Quotes at the end of each line…

:grin:

2

JS does have issues with multi-line strings. Not sure if there is a way around this.

We had a similar discussion using native JS replace() function on Entity Custom Data field that was a Widestring Address containing line-feeds. The eventual explanation on how the field was evaluated in JS made sense as to why it would not work. Not sure if it was “fixed” …