Dynamic Combiner componentlist updation

Hi,

We are trying to update Target quantity (in table componentlist) in combiner dynamically, and following below code

createinstance(node("/Combiner",library()),model());
treenode combinernode = last(model());
-----
then we are drawing connection to racks and queue from combiner afterwards we are trying to update target quantity.
---
treenode componentlist=getvarnode(combinernode,"componentli st");
settablenum(componentlist, 2,1,10);

Unfortunately not able to update combiner target quantity dynamically,have tried most of the options, don't know where i am making mistake.

Kindly advise.

Thanks in advance.

Regards
Shashank Trivedi

Good point. The object relies on a reset or click to create the table...

For now just add this line before you set the values:
settablesize(componentlist,nrip(combinernode)-1,2);

Thanks alot jason for your kind reply.
We have very simple model one source (source-1) connected to one queue and same queue connected to combiner on port-1 and for combiner port-2 , one queue followed by one source.

Now we are combining items from these two sources and pack quantity is defined dynamically as per item type from source-1, item types are defined using the function duniform(5,10,2).

We are using following code in on entry trigger in the combiner.
/**Custom Code*/
treenode item = parnode(1);
treenode current = ownerobject(c);
int port = parval(2);
int value= (getitemtype(item));

treenode componentlist=getvarnode(current,"componentlist");
settablesize(componentlist,nrip(current)-1,2);
settablenum(componentlist, 1,1,value);
setvarnum(current,"targetcomponentsum",value);
pf(value);

Unfortunately model is behaving very erratic and not doing packing correctly as per required pack quantity.

Attaching model for reference as well.

Kindly advise.
Regards
Shashank Trivedi

Usually you'd only change the component list for items that arrive on port 1, but there's no test for that in the code you've posted.

By the way - a lot of code problems are easily solved by placing a breakpoint in the left margin and stepping through the model events and then the code while observing the local variables.