seansy-archy - Another question I had, I submit...

Another question I had, I submitted a ticket for this, but thought maybe someone here could identify the issue. We use Custom Actions on answers heavily to customize our users' experience in embedded liveboards. However, I have noticed the following issues with column data passed back through custom actions: 1. Columns aren't in the order that they're displayed to the user 2. Columns don't have any aggregate values for the columns that have SUM, AVG...etc. The metadata is included regarding what aggregate formula is applied to a column, but the values (for example the sums of columns) aren't present. 3. There is no metadata around which columns are hidden/shown to the user in the answer. 4. Column names aren't consistent with what the user sees. For example some columns that have been renamed don't show the renamed value (See screenshot regarding Day(Last Wallet Activity Date) vs Daily Last Wallet Activity Date. As a result, we're fairly limited in the experience we can provide to our users. Is there a more complete version of data available to clients in Custom Actions?
No description
No description
10 Replies
Aditya
Aditya5d ago
Hey @seansy-archy 1. We are checking this internally. Can you please also raise a support ticket for this? 2. I didn't get you what you are trying to ask here. Can you please explain a bit more on what are your expectations here? 3. We can use headlineVisibilityMap to know which columnId is visibile and which is not. 4. Please raise a support ticket so that correct team can check on this.
eric.silva
eric.silva4d ago
Hey I'm experiencing something similar where I have an Answer who's columns are in an order, but the API (data endpoint) returns something different entirely.
seansy-archy
seansy-archyOP4d ago
@Aditya - 1. case No. for ticket is 00392636 2. It's fairly simple -- how is the user currently viewing the embedded table? We'd like the payload data to represent that so we don't confuse the user with a different layout in the Custom Action. - Columns should have the same order that the user sees - Columns should have the same names that the user sees - Any column aggregates (sum avg...etc) we would also like available in the payload associated with the column to show to the user. - Any hidden columns in the visualization we want attributed with their hidden state. These data are currently not available in the current state of the Custom Action Payload (column names are inconsistent, sometimes they're correct). I have looked through the payload JSON thoroughly, happy to help show where the gaps are. 3. I already tried using headlineVisibilityMap. That doesn't do what you think it does. It represents what columns have "Display Summary" enabled, with an aggregate formula for the column (see attached). 4. Support ticket is 00392636
seansy-archy
seansy-archyOP4d ago
No description
No description
Aditya
Aditya4d ago
I see. I am checking internally with the team and will update you. @eric.silva can you please mention what API are you using where you see this inconsistency?
Justin Mathew
Justin Mathew4d ago
@seansy-archy @eric.silva have you tried using the AnswerService.fetchData ?
Aditya
Aditya4d ago
This will also return the same data.
Aditya
Aditya3d ago
Hey @seansy-archy For getting columns in order, you can use orderedColumnIds array(Please look at the attached screenshot). This will be an empty array if it is in the default order. Similarly, if you want to find which columns are hidden, you can look for columnProperties inside vizProp. Please note that elements in the columnProperties array will come up only if you hide some elements.
No description
seansy-archy
seansy-archyOP3d ago
awesome! Thanks @Aditya, is there documentation of this anywhere? regarding the column names being incorrect, it seems like a bigger issue -- they're also wrong in the exports for a given answer Created an issue for the export part Case No. 00392938
varath surya
varath surya3d ago
hey @seansy-archy regarding the column aggregates it is not available in the current payload since the payload data is paginated and the headlinedata is part of different response. For column names being incorrect in the payload, if the user has changed the column name it will be the same as the payload but if not we processes the the name based on different properties of the column and the locale that is used.

Did you find this page helpful?