Hi all,
In a protocol, a user found a table with an ArrayOptions tag different than 0:
When creating a service using parameters from that table using the primary key as index, the parameters never show at the service:
Is it possible that a wrong definition in the table triggers this miss behavior?
Also, this DMA version is 10.1 CU4, the user still has 9.0 where it is working.
Thanks.
Hi Edson,
Looking at the latest development guide I found this:
Primary keys
A table must always contain a column that has a unique value for every row in the table and which is used to refer to a row unambiguously. This is typically referred to as the primary key. The index attribute of the ArrayOptions tag defines the column index of the column that holds the primary keys.
Please keep the following guidelines in mind for primary keys:
- The first column of a table should hold the primary keys (index = 0).
- The column that holds the primary keys must be of type "string".
- The primary key does not have to be user-friendly and should be as small as possible.
- A primary key must not have leading or trailing whitespace.
- Semicolons (“;”), question marks (“?”) and asterisks (“*”) must be avoided in primary keys as these characters have a special meaning in the dynamic table filter syntax and could therefore cause table filter queries to be interpreted incorrectly. (Refer to the "Dynamic Table Filter Syntax" section in the DataMiner help for more information on the filter syntax.)
I think in the most recent versions of dataminer that behavior is now expected as default.
Hi Arturo,
Definitely, the ArrayOptions different to 0 is breaking the service, the best option will be to follow the development guidelines to avoid any issue.