Insert record with composite key...
I use composite keys often (primary keys composed of two or more columns).
Using the Insert Record behavior, the tool requires a "Save inserted ID in Session".
I tested this and it saves a composite key session value of "0".
This doesn't matter as the composite key is made up of 'known' values.
Thus my point...why require the variable be set if it has no use in some instances?
Right now I am labeling these as NAname (NA as in not applicable)...but they muddy up my interface. I am in the process of wiring up table 5 of over 40...I don't want a mess of unusable variable floating around.
Am I missing something here, or can this requirement be removed...let the developer set the variable if they want it.