TM1 Forum

Does anyone know how to identify the parameters used in the TM1 Contributor Control Processes?

We are trying to potentially run these on the back end but need to know what to supply for the parameters to make it work.

pExecutionId
pAppId
pControl

etc.


Thanks

I don't have a server with Contributor with me at the moment, but from memory...

pExecutionId can be set to anything you like, but make it unique for each time you call a process. You can then pass it on to any other processes that might be called via ExecuteProcess from within the process you are executing. The value gets written to one of the }tp cubes and is used as a semaphore, hence why it needs to be unique. I based mine on TM1User and Now.

pAppId is the value from the }tp_Applications dimension associated with the contributor application. You will have as many Level 0 elements in this dimension as you have applications defined on the TM1 Server, most likely only 1.

pControl needs to be set to Y, which in turn prefixes object names in the process you're calling with a } meaning that if the Y isn't supplied the process fails as objects that the process is looking for won't be found.

In short, yes you can successfully use the Contributor processes to perform all the Contributor functionality without using the Contributor front end.