Try this: Create a package with the Operator you want to modifyThen, copy the Operator bracket of the package, assign its value to the op variable in this js code and add the <access noConsoleCnx="true"/> to it, in the same place of my example. Execute it and it will change itvar op = '<operator lab...
Hello, it seems to have been changed in the last Adobe Campaign version. May you try to by pass it using a JavaScript code? You've to set access/@noConsoleCnx to 1 Try this: Create a package with the Operator you want to modifyThen, copy the Operator bracket of the package, assign its value to the ...
Ah! I haven't faced this as i'm not in that version. Perhaps you could by pass it by creating it with a java script query or a direct SQL insert? xtk.session.Write(<operator _operation="insert" xtkschema="xtk:operator" password="x" name="y" (...) />); Or, with an SQL Code, you can look at the table...
But how to explain, i'll tell you the steps we did Truncate table - Data loading - Deduplication using the primary keys - update data. This would remove like 10 % of the data, but we still get duplicates. Then I tried with the enrichment, and would insert only 1 record. I've checked the data itsel...
This didn't work we're trying to recreate the workflow because it's the only one giving us errors. I think the main problem is, it's detecting as duplicates records that are not duplicated (If I generate the INSERT INTO codes, they're not duplicated!)
Can you give me more information about this? Like, the connection settings will be different in those external accounts? Will the number sender change?
Hello, I'm having a problem and I don't have any more idea of how to fix it. I have a workflow that insert registries into database, first read a file, then deduplicate the data and then insert it. The Data schema has a compound primary key of 6 different attributes, defined like this: Then In the d...