Some props writing out in a loop, others not. Why? | Community
Skip to main content
M
morgant29080047
New Participant
August 20, 2019
Solved

Some props writing out in a loop, others not. Why?

  • August 20, 2019
  • 13 replies
  • 9599 views

I'm manually setting and submitting an array of document titles in custom code in Launch when a user executes an action. However prop47 isn't getting stored in analytics but it looks like it's getting set in both the Adobe debugger and the console. The data is correct but it's not getting stored. Prop50 is the same value (business requirement, don't bother asking why the duplication) and it is working. Any thoughts on why?

Here's the loop:

for (var i = 0; i < docLength; i++) {

      var s=s_gi(xxxxxxxx);

      s.linkTrackVars='prop1,prop47,prop50';

      s.prop1=articleIDs[i];

      s.prop47=myDocs[i];

      s.prop50=myDocs[i]; //stores title in the all titles prop

      //console.log('in loop' + myDocs[i]);

      var interaction = myDocs[i] + ":copy links inline";

      s.tl(true,'o',interaction,null);

      s.clearVars();

      s.prop1='';

      s.prop47='';

      s.prop50='';

    }

Here's a screenshot in the debuggers showing the data;

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Andrey_Osadchuk

Since both prop47 and prop50 are sent correctly (as per the screenshot), I would double check the Processing Rules that may overwrite prop47 (similar to VISTA rules if you have them).

13 replies

Show previous replies
Andrey_Osadchuk
Andrey_Osadchuk
New Participant
August 21, 2019

Then I would assume that the scenario you have just described does not match the initial screenshot .

Try to find out maybe there is another code in the s_doPlugins of the extension custom code, or in other Rules that may be processed  prior this rule.

    M
    morgant29080047Author
    New Participant
    August 21, 2019

    That's a good thought but no, no processing rules.

    I feel like there's a lot going on in my rule here. I'm looping through this array (a dynamically created data element) and processing that in a custom block under conditions, then after that I'm setting some other props in the set variable block and then I'm calling a fire beacon to save those. I don't know, i feel like somehow all this is stepping on each other. The set variables are getting consistently written out, but the stuff in the loop I'm not sure what's getting consistently written out and what's not at this point. Part of the issue is how the business/client wants the data, some changes to the front end of the app, etc.

    Andrey_Osadchuk
    Andrey_OsadchukAccepted solution
    New Participant
    August 21, 2019

    Since both prop47 and prop50 are sent correctly (as per the screenshot), I would double check the Processing Rules that may overwrite prop47 (similar to VISTA rules if you have them).

      Terms & ConditionsAccessibility statement

      Loading footer...