How to force Transform Map scripts to fire on Update (PUT) to Import Set ?

[dazed]

Hi

I am successfully POSTing to an extended Import Set Table and linking this (via Table Transform Map) to a Change Request.  The Transform Map has a coalesce on "number" field.

The POST (insert) creates a record in the Extended Import Set Table and fires the Table Transform Map and onBefore script.

A further POST to this table creates another record (also linked)

This isn't what I want - I would like to update the Extended Import Set table and fire the Table Transform Map again.

So I am attempting to PUT to the table to update the record - this works - BUT the Table Transform Map doesn't run (doesn't push field updates through) nor the onBefore script.

Is this "by design" or am I missing a way to force the Table Transform Map to run?

[Dubz · Accepted solution]

You shouldn't need to ever PUT to an import set. You POST the new data in and then use coalesce values in the transform map to ensure that existing records are updated instead of duplicates being created.

[dazed]

Thanks David - I was misunderstanding (as a newbie trying to adjust an existing application) the role of the import set and tranform maps.  I have the coalesce set so the POST isn't creating a new Change Request, I was just trying to avoid creating lots of Import Set records - but I guess these are effectively an "audit" of changes that have been applied. 

[Dubz]

Any records you import to these tables are transformed and then periodically discarded. There's a scheduled job that runs on your import set tables that clears out old import set data, i believe it runs every 7 days by default. You can see the details in the Scheduled cleanup module in the import set application. 

If you question has been answered please can you mark my answer correct to close the thread down?