1
0
-1

Am I understanding correctly that we can no longer dump a string into a data field, as an "initial value"? Seems the “initial value” data property is no longer available, and the only way to get a string into this field is to put it in a calculation. Is this the new model? (See image below)

I’m not suggesting that this is a bad thing or necessarily causes an issue (I assume that mandating this solves a different issue that I don't understand), but it does change the way that I normally build solutions, and it would be helpful to understand the thinking around this architecture.

Subsequently, I need a better way to define large, multi-line strings, and my knowledge of JavaScript is dangerous enough to have created some very messy code, and I was wondering if you knew of a more elegant way to do things? Currently, I need to either escape each line of my string in order to make it fit into a script, or I need to join 1000 lines which is a little unreadable.

In my final solution, the string will be prefilled by a TM service, but during the build-phase, it's important for me to have this data defined in-form.

 

 

    CommentAdd your comment...

    1 answer

    1.  
      2
      1
      0

      Hi Sacha,

      Ensure that the 'Include in Submission Data' checkbox is selected and you will be able to add an initial data value to the Initial Data field under the Transact Integration section.


      Cheers

      Chantal

        CommentAdd your comment...