Hidden place to store information on an element?

[Colin Richardson]

Hi,

I'm pushing elements to various third party systems and keep synching information (ids) in a separate database.

Anyone know of some hidden location in an element I can get to only via automation to store this information instead?

I've thought of creating locked "mapping" elements, but that's a bit  (lot!)clunky.

~ Colin

[skiwi]

Won't the GUID do for this?

[Colin Richardson]

You *could* though I don't feel comfortable bastarding the GUI...

If you have 5 interfacing sytems you'd need to come up with an algorithm to create the GUID.  It'd also be dangerous because some of the PDATA fields are generated based on GUIDs, so there'd be a nasty roll on affect.

Trying out my first workflow scripts which looks promising.  Then I'll just use tagged values and then prevent people outside a security group doing anything with it... now if only I can find some workflow examples.  Luckily there's a lot of VBScript samples