Scenario:
I want to update the table with latest information before I ask for information from table so that I have the latest information. Table auto-update every 1 min but I need to update also when required.
Tables of data (and any other metrics for that matter) are updated based on logic defined in the drivers for that element. This could be time-based, but also based on specific events occurring (such as on start of element, or when another metric has a specific value, etc.), or sometimes a combination of both. Some drivers would have a button (e.g. load or refresh), which provides an event-trigger to load the table. If that's the case, you could call that trigger from your automation. But not all tables of data have this, and it would be rather the exception than the norm. I'm not a developer myself, but I believe that this would be the only way to achieve that, i.e. to have a hook in the driver that serves as a trigger for the polling of that data.
The only other thing I was thinking of is the TIMER BASE, i.e. this is a general metric that is available on all managed elements and which allows you to accelerate or decelerate the polling on that element (i.e. the timer base allows you set the polling 10 times faster). But that's not really a solution, because if you happen to have a table that is only set to be polled once each 10 minutes (which is unlikely to be the case, but just as an example), you can make it only poll within 1 minute then (i.e. in your script you would not be aware of that 10 minutes defined in the driver, and you only know that it will be 10 times faster and not how fast it will come).
Maybe some other people have some further thoughts on this...
Does that mean that between the two calls you are also executing a control / setting (i.e. you want to verify with the second call if the control had the desired effect)? If so, question is also if you do that control also via DataMiner. Because in general if you perform a setting on a configuration metric via DataMiner, then DataMiner will instantly poll that data again from the managed product. This is a general best practice normally applied for any driver (to ensure that if users perform settings, that they can immediately see if that was succesfull and don’t have to wait for the timer-based polling to occur). Just FYI. But you are referring to a table, and there we have to be a little bit more careful, because those can have different underlying and more complex structures.
So my automation script creates service into MSA and before creating second service I have to update table in MFVP controller in dataminer so that I have the next available server otherwise for the next call I will get the same server used for the first call because table is not updated yet.
Thank you so much prompt reply…driver does not have a refresh button..for me required to have updated information because the automation script is going to be used by API call so if dataminer does not completely update table and second API calls started to process will lead to failure for other calls. so if there is a way to update the table before processing the second request I can avoid that situation.