Question 1: When using the “runQuery” and “getAllMeasures” and related APIs to implement our own FieldsList, fields with level seems very tricky. Sub-level fields share the uniqueName with the top-level field, but after we add the sub-level field to “column” or “row”, the pivot always show the top-level field. However, the built-in FieldList does not have this problem.
Question 2: This one is about the date string field. After adding one to the “column” or “row” and click the filter icon, the label filter or date filter are sometimes set “display: none” (by js probably, because it’s inline style). After sync the report data with the old version (with built-in) FieldList, it works correctly.
Are there some inner workings that are not covered by the public APIs related to date and level field type?
Thank you for writing to us.
We would like to confirm that the Field List’s functionality can be achieved with the available API calls.
To display a field starting from a certain level, the level name needs to be specified for that field in the
slice object that is passed to
runQuery(), for example:
levelName: "Product Name"
Also, it is possible to check how different representations are achieved by applying the desired settings through Flexmonster’s UI (for example, the Field List), saving the report and seeing how the configurations are applied.
Please let us know if this helps.
Looking forward to your reply.