I'm having trouble with onComplete Transform Scripts...

[daigonite]

Hello, this is my first question here, I'm sorry if it doesn't make much sense.

Anyways, I've been trying to run an onComplete transform script that essentially queries through specific records and deactivates them. Seems simple, right? Well it's not the code that's bugging me, but rather the onComplete transform script never seems to actually run. When it's onStart I have no problems but even just having a gs.log statement seems to cause it to completely ignore my script. Does anyone have any idea what I'm doing wrong? Is there some property of transform maps that causes them to sometimes not execute the onComplete transform script?

[daigonite]

I disabled the other scripts and it still is not printing any log statements.

[daigonite]

As a test yesterday, I modified the script so that it inserts a record on a simple table (in this case kb_feedback). Yesterday, it managed to insert a record, however today it does not. It seems to be functioning very inconsistently.

[Stijn Verhulst3]

Rachel,

do you enforce mandatory fields or run business rules on the transform map?

[daigonite]

Mandatory fields are not enforced. Business rules are ran.

[bernyalvarado · Accepted solution]

Hi Rachel,

I believe that your script may be running even when you don't see your log statements . odd ha?! try using a different logging mechanism. Perhaps the one that is used as an example out of the box for the LDAP transform scripts.

You can use the following statements to log:

log.info("Testing: Here goes some info");

log.warn("Testing: Watch out for that warning");

log.error("Testing: Houston, we have a problem!");

I believe you should be able to see the log results in the table import_log.

Do take in mind that this will require that log is defined in the onStart transform script on the following way:

gs.include("LDAPUtils"); var ldapUtils = new LDAPUtils(); ldapUtils.setLog(log);

I hope it helps!

Thanks,

Berny