I'm working on protocol that has following SNMP table:
The issue is that we are getting wrong primary key value. For example, we are getting value 6 instead of 5. It's not only for this table, like it is visible on image above, there is FK column and 15 more tables that are in relation and getting wrong primary keys.
I would need to change it to correct values. I tried with <Sequence noset="true">min:1</Sequence> tag in primary key parameter but it will not work because type of primary key need to be string.
Adding new column with type="retrieved" in which I can store custom value will break SNMP, I guess.
Also, this primary key is NotAccessible (from MIBs) and options on OID are instance and multipleGetNext. I'm not sure how can I do manipulation on primary key with instance option on OID.
Is there any idea how can I modify primary key values in this case? Only solution that remains is to hide current SNMP tables and create 15 new tables that will have custom and correct values for primary keys, which is bad solution. Does anyone have something similar? Any ideas?
To my knowledge it's not possible to manipulate SNMP instances.
Depending on how important it is to have the 'correct' primary keys, I only see 2 solutions:
- Create an additional column representing the correct value calculated from within QAction -> The instance will still remain the same
- Create a table -> The instance will be the new calculated value