How to Find the Personalized View for a User or Analysis File in the Spotfire Database
Article ID: KB0080311
Updated On:
| Products | Versions |
|---|---|
| Spotfire Web Player | All Versions |
Description
The personalized views allow users to continue where they left off from one time to another when working on the analysis in the web client. These personalized views (analysis states) are stored in the database on close or timeout of the analysis by the given user.
Issue/Introduction
How to Find the Personalized View for a User or Analysis File in the Spotfire Database.
Resolution
The personalized views are stored in the table LIB_ITEMS (and related tables like LIB_DATA, etc) where LIB_ITEMS.ITEM_TYPE='04a1dc4d-6794-4c49-b91b-063de8a77450' (which corresponds with LIB_ITEM_TYPES.TYPE_ID which has a LIB_ITEM_TYPES.LABEL value of 'analysisstate'). You can find the personalized views by querying the database.
For example (requires updating of the GUID with the GUID of the DXP being queried):
Disclaimer: The content of this article is for informational purposes only. The subject material may change in any new versions with no notice and there is no responsibility by TIBCO to maintain or support future access to this internal application content. Modification of any internal application content is not recommended and can lead to an unsupported configuration. It is not intended to be used "As Is" in a Production environment. Always test in a Development environment.
For example (requires updating of the GUID with the GUID of the DXP being queried):
select lit.LABEL, u.USER_NAME, li.* from LIB_ITEMS li join LIB_ITEM_TYPES lit on li.ITEM_TYPE=lit.TYPE_ID join LIB_RESOLVED_DEPEND lid on lid.DEPENDENT_ID=li.ITEM_ID join USERS u on u.USER_ID=li.CREATED_BY where lit.LABEL='analysisstate' and lid.REQUIRED_ID='3d4d44af-5b32-4cf2-b83e-acc8fa9a45ba'--Replace with GUID of DXP in question
Disclaimer: The content of this article is for informational purposes only. The subject material may change in any new versions with no notice and there is no responsibility by TIBCO to maintain or support future access to this internal application content. Modification of any internal application content is not recommended and can lead to an unsupported configuration. It is not intended to be used "As Is" in a Production environment. Always test in a Development environment.
Feedback
Yes
No
Powered by
