How to automatically load a milestone collector with a processflow?
1. I don't know. I asked this as a follow-up under this post.
2. The available parameters differ slightly between object.copy() and createcopy() (use ctrl-f to find the command). But "object.copy(dest)" and "createcopy(object, dest, 1)" should give the same result.
3. Once the query of the Calculated Table is defined it doesn't need any pointer references to other nodes to function, so you could simply copy it into the model like the stats collector.
// Check if calculated table is present in the model
treenode calcTables = Model.find("Tools").subnodes.assert("CalculatedTables");
Object table = calcTables.find("MyCalcTable");
if(!objectexists(table))
{
// Copy the table into the model
table = current.subnodes["MyCalcTable"].copy(calcTables);
}For the table to be shown in the query builder interface, you would need to add a coupling node to the respective table (yellow, under "tables" variable node) and link to that node in any expressions (pink).
Does the link structure match that shown below (coupling node to stats collector under "tables" and the "table" node in the expression tree points to that)? When I recreate that structure in my example library the current value of the "Count When" dropdown is correctly retrieved.
Or could you share an example of yours so I can check it?
When opening the Calculated Table GUI and the "column" node is present in the expression's subnodes, then it should check if a column with that same name exists in the linked table and set that as the starting value for the dropdown menu.
I've tested this again with a global table and the pre-configured settings stay after adding the table via the library.
It should only default to the first column if the link in the "table" subnode is not properly set. See excerpt from the coldlink code below that populates the menu. (You can access this by right-clicking in the GUI and choosing "View -> Explore Structure". This is a useful function in general to inspect the code behing GUI elements.)
Hi, @Felix Möhlmann ,
apologies for keep bothering you with this. Would you be able to tell me what I am doing wrong here?
Case A: a dummy object encapsulates the real object, to be able to call a dropscript and install flows, milestone collectors, etc. (as you suggested above).
Result: does not work (object drawing wrong/interrupted, no conveyor system objects - transfer types, etc. - brought in, no object flow brought in)
Case B: instead of referring the encapsulated object, the dropscript points to a copy of that object directly on the library root folder.
Result: it works, flow brought in, object successfully drawn. However, the object also appears in the library menu.
I could send you the code, but in private, as this is company material. Please let me know and thank you very much once more.
Interesting. When I add an object similar to yours (containing conveyors) to a library, the conveyors' visualization node points to the visualization object that gets added to the library alongside the actual object (when using the rightclick menu).
When I drag this object into the model or use a dropscript to do so, this reference gets changed to the conveyor system that gets created in the model.
For some reason this does not happen when the dropped object is placed inside a dummy object.
When I update the pointer in the dropscript, the conveyors get drawn correctly after dropping the object.
