Hello Team,
How to find out the Navigating URL for adding display file from thick client to web
Regards,
Phani
Solved! Go to Solution.
Hi,
When you publish a display to the web it goes to ..\Prognosis\WebUI\IIS\Dashboards\User\.
When you add the dashboard to the WebUI Navigation pane, a lot of time you just need to put the Dashboard name in there IF there are no or minimal prompts associated with the dashboard. Figuring out the prompts though is the most difficult part of adding it to the web. (see below)
A good starter URL to The URL though if just the dashboard name itself doesn't work is:
https://<server>/Prognosis/Dashboard/<Dashboard Name>?DefaultNode=%5c<Nodename> &DefaultAssociate=%23AllAssoc
Then you find the red dots on the display and collect a list of them to find out which ones it is looking for and then add each of them to the URL by adding "&<promptname>" to the end of the URL... order doesn't matter as long as it is after the "?DefaultNode=%5c<Nodename>" (which can also be entered as just "?Defaultnode=\<Node>" and your browser will translate it.
A simple example is a URL with a few additional prompts is:
https://<nodename>/Prognosis/Dashboard/AIM%20ATM%20Details?defaultnode=%5c<Nodename>&defaultassociate=%23AllAssoc&atmid=<value>&atmlocation=&rptdatabasenode=%5c<value>&defaultdbnode=1
The easier way is actually look at the dashboard you are publishing and look for the #prompts usually located in the WHERE clause and the user fields and list all of the #PROMPTS used and ensure they are in the URL when you add it to the navigation pane like #ATMOwner below becomes "&ATMOwner=<value>".
Mashups are similarly stored in the same path except they are in this format.
<domain>_<user>_Watchlist_<Mashupname>.dashboard.
Hi,
When you publish a display to the web it goes to ..\Prognosis\WebUI\IIS\Dashboards\User\.
When you add the dashboard to the WebUI Navigation pane, a lot of time you just need to put the Dashboard name in there IF there are no or minimal prompts associated with the dashboard. Figuring out the prompts though is the most difficult part of adding it to the web. (see below)
A good starter URL to The URL though if just the dashboard name itself doesn't work is:
https://<server>/Prognosis/Dashboard/<Dashboard Name>?DefaultNode=%5c<Nodename> &DefaultAssociate=%23AllAssoc
Then you find the red dots on the display and collect a list of them to find out which ones it is looking for and then add each of them to the URL by adding "&<promptname>" to the end of the URL... order doesn't matter as long as it is after the "?DefaultNode=%5c<Nodename>" (which can also be entered as just "?Defaultnode=\<Node>" and your browser will translate it.
A simple example is a URL with a few additional prompts is:
https://<nodename>/Prognosis/Dashboard/AIM%20ATM%20Details?defaultnode=%5c<Nodename>&defaultassociate=%23AllAssoc&atmid=<value>&atmlocation=&rptdatabasenode=%5c<value>&defaultdbnode=1
The easier way is actually look at the dashboard you are publishing and look for the #prompts usually located in the WHERE clause and the user fields and list all of the #PROMPTS used and ensure they are in the URL when you add it to the navigation pane like #ATMOwner below becomes "&ATMOwner=<value>".
Mashups are similarly stored in the same path except they are in this format.
<domain>_<user>_Watchlist_<Mashupname>.dashboard.
Members | Likes |
---|---|
43 | |
36 | |
23 | |
17 | |
16 |