Hello Team -
Part A ]
I am trying to Use URL action in the visual below :
This is how my ideal setup look like before implementing URL action -
Dynamic View is :
ifelse(
${DynamicView} = "SKU", {Brand SKU},
${DynamicView} = "Brand", Brand,
Retailer
)
Here, when I select Retailer under Dynamic View, even though two product types (Blenders and Monitors) are selected in the top Product Type filter, the visual displays three entries based on the unique retailer, brand etc.
Part B ]
I am now trying to embed a URL action in this visual so that when a user selects SKU under Dynamic View, clicking on a SKU takes the user to that SKU’s product page in our app.
URL setup is - https://app.ABC.com/products/discovery?categories=<<Category_ID>>&brands= << Brandname>> &part_numbers= <<SKU>> &firstSeenFrom=2022-01-01&firstSeenTo=2030-01-05
In this case, three fields need to be dynamic and included in the visual: category_id, brand_name, and SKU.
I have tried two different setups. In both cases, the URL action works correctly, but the granularity of the visual changes.
-
In this setup, I used dataset-level fields (category, brand, and SKU) and kept them hidden in the visual. While the URL action functions as expected, it impacts granularity.
For example, when I select Retailer under Dynamic View, and two product types (Blenders and Monitors) are selected in the top Product Type filter, the visual shows multiple entries per retailer. A similar issue occurs when selecting Brand.
However, I Need only three entries, as shown in Part A.
- I have tried one more approach here again by creating fields for brand and SKU like below:
Brand for URL
ifelse(
${DynamicView} = ‘SKU’,
{Brand},
null
)
SKU for URL
ifelse(
${DynamicView} = ‘SKU’,
{SKU},
null
)
Since I want the URL action to work only at the SKU level (and not for Brand or Retailer), I have configured it accordingly. The action itself works as expected.
However, the granularity issue still persists. For example, when I select Retailer under Dynamic View, and two product types (Blenders and Monitors) are selected in the top Product Type filter, the visual shows six entries three per retailer. A similar behavior is observed when Brand is selected. (for single product being selected lets say only monitor then this approach does work well)
What I am trying to achieve is to enable the URL action in this visual without introducing multiple grain issues. The visual should behave exactly as shown in Part A, while still having the URL action enabled with the required fields.
In other words, the URL action should work only at the SKU level, but the visual grain should remain consistent when Retailer or Brand is selected under Dynamic View, without creating duplicate entries.
I understand that having unique multiple retailers will create multiple entries, but the visual should not duplicate beyond the selected level. The granularity should stay consistent with the chosen Dynamic View.
As shown below, selecting all product types returns unique retailers, without repeating retailers for each product type (and the same applies to Brand).
Note -
- https://app.ABC.com/products/discovery?categories=
<<Category_ID>>&brands=<< Brandname>>&part_numbers=<<SKU>>&firstSeenFrom=2022-01-01&firstSeenTo=2030-01-05 - This URL is Fixed and cannot be changed. - I can’t use the Dynamic View parameter directly in the URL action.
If i use dynamic view parameter in the action then : If SKU is selected in the parameter, Brand also resolves to SKU in the action. This causes incorrect URL values.
Expected:
<<Category =12>>
<<BrandName>> = ABC
<<SKU>> = 123
Actual when SKU is selected in Dynamic View:
<<Category>> =12
<<BrandName>> = 123
<<SKU>> = 123
Because of this, we need separate fields for Brand ,SKU and category in the action setup which is what introduces the granularity issue in the visual.
So - i) Do we need to change the URL action setup, or is there any visual-level workaround to make the URL action work only for SKU, while keeping the visual behavior the same as shown in Part A? Also, how should this be configured if the visual is a pivot table?
ii) Is there a way to configure the URL action so that users can click only on SKUs, and not on Brand or Retailer?Ideally, the “View product on app” action should be available only when SKU is selected, and be disabled for Brand or Retailer views.
Please help here
Thanks.
