Passing Parameters with Anonymous Link embedding

Question & Answer
, , ,
1

Hi,

It has been implied that if you follow the rules for parameter passing in URLs with an anonymous embed URL then the parameter will be passed to the dashboard. But when I have tried this the parameter either doesn’t work (if after the query separator ‘?’ i.e. [dashboardid]?code=[code] etc… #p.[parameter]=[value]) or is actively removed (if before ‘?’ but following a fragment separator ‘#’ ie. [dashboardid}#p.[parameter]=[value]?code=[embedcode])

Am I missing something or can you not pass parameters with an anonymous embed?

2

Hi @lstablefordmatrix

You should be able to pass parameter with anonymous embed url.Can you please check if the parameter is correctly spelled. Also, if you are not launching embed url in the browser directly, I recommend you to use the embedding SDK to pass the parameter to the dashboards.

Regards
Vetri

3

Hi @n_vetri

FURTHER FURTHER EDIT: Upon reviewing my test set up it turns out that a change I made to user config (which set up the RLS tag) had not saved. When I reset this value the dash worked as expected thus accidentally proving what happens if your parameter value does not match an RLS approved tag for the user you are signed in as. Irritating that my save didn’t work but I have properly kicked the tyres on these systems and now know that they work.

FURTHER EDIT: I added a control for the parameter to the embed in order to test further and was amazed to find the parameter WAS being set, but if you look at the dash in QS with the param set you get data and in the embed you get the “There is no data” message.

It should be noted that RLS is being implemented in this dash in addition to parameterised datasets. Could that be causing the issue?

EDIT: Consulting my yarn.lock told me my version of the SDK was too low. Once I upgraded I tested that the contentOptions were being applied by removing the undo/redo buttons on my embed, and that works fine. As for applying parameters it would appear all that happens is that the parameter set puts

#p.[ParameterName]=[ParameterValue]

on the end of the URL, which continues to have no effect on the render. So, contentOptions are being applied but the parameter and value are not currently being read. Any ideas as to why that might be?

Original Post

Has there been a change? When I import the SDK like this:

import * as QuickSightEmbedding from ‘amazon-quicksight-embedding-sdk’;

and attempt to createEmbeddingContext like this:

const embeddingContext = await QuickSightEmbedding.createEmbeddingContext();

I get the message:

export ‘createEmbeddingContext’ (imported as ‘QuickSightEmbedding’) was not found in ‘amazon-quicksight-embedding-sdk’ (possible exports: __esModule, embedDashboard, embedQSearchBar, embedSession, embedVisual)

If I just skip straight to ‘embedDashboard’ i.e. make the call:

await QuickSightEmbedding.embedDashboard(frameOptions, contentOptions);

the Parameter values aren’t applied, although no error is returned. It appears the contentOptions are just not applied.

Am I doing something wrong?