XMPIE data error

[C. Bell]

I am encountering an error where the data is pulling in backwards on some fields in ucreate. For instance, the first sequence number is "0001", but it is pulling it in as "1000" on my document. It also has occurred with zip code numbers being reversed as well. 

Has anyone else ever encountered this problem? Is there a reason for it that anyone discovered? I am trying to figure out the cause, but I am unsure as of right now..

I am currently running ucreate 12.4 with Indesign 2023.

Any help is much appreciated!

Thanks,

Charlie

[SteveL]

Hi Charlie,

Are you able to test with a current version of uCreate Print to see if the same problem happens with the latest version?

[west-digital.fr]

I assume that you don't make use of any custom JavaScript function that would apply this reversal ;-)

I can't remember that we and none of our customers ever experienced this behavior, regarless the version.

You said "on some fields". Does this mean that "other Fields" don't show this behavior? Have you determined any shared characteristic of all those which work, against all those which do not? (per instance: those which have numeric values fail, whereas those which have alphabetical characters won't?).

Also, you said "Fields". Does this mean that the behavior is really related to Fields, but not to Content Objects? To sort this out, I would simply edit the rule of a "wrong" Content Object, changing its related (wrong) FIeld against another Field that proved being OK in another Content Object; if the wrong behavior stops, then it's indeed related to the Field; if the trouble persiste, then it's more related to the Content Object, or its tag in the InDesign document (per example - you never know - a text that would be set in Arabic or Hebrew??).

If you really suspect that the trouble is related to the data, then you could investigate a bit more with the "ReportMessage" QLingo function, which- as its name may indicate - would add messages in the uCreate popup, at the end of a print production; so, consider coding something like

ReportMessage("My suspected field value=" & |->[myField]) |->[myField]

Again, if the ReportMessage outputs correct values, I would investigate the document.

west-digital.fr

[C. Bell]

Unfortunately, I just have access to the older version at this time.

[C. Bell]

I think it has something to do with the text box in Indesign. I reset the text box and it is fine. The preview in the xmpie palette shows the data correctly, but just the text box was showing it in reverse. So the data seems to be ok.None of the other fields being pulled in through content objects are having any problems in my document. I will try this "reportmessage" function next, thanks!