Personal views in Alliance v15.4.4

Hi Melissa,

i don’t believe the application supports export, import of personal views. Primarily because these are personal to the user whereas organization views are for all users.

However having said this, I am guessing you want to move personal views from one environment to another that are using the same version of Alliance without copying the complete database. I think it is important to understand that a specific view from one DB may not work well on another DB. Reason is you may have custom fields added which also are in the view information that may not be aligned between the two database profiles. Or even the setting to ignore culture with views on miscellaneous I module might also interfere. I would consider this only as a backup in case the setup was corrupted for the same database and you needed to revert back somehow  e.g. a new view was saved over an old view with the same name. 

The views are stored in the table cp_application_views if you want to review them in general but again I don’t think you can export/import the personal views directly  I suppose with a bit of SQL you could set all the views to organization views and then export them but after importing them set them back to personal  if you want do something without actual code changes right now  

Hi Phil & Melissa, we ran into the same issue and reported this as a bug.  It was fixed for us in a “quick fix” release, but I believe it was also going to be added to standard product.  Our reference ID was US0069462.  Hope this helps.

Regards,

-Nick

Thank you, Nick.

I did not hear about this but will check out the lead you just provided.

It still surprises me that an export in the application setup guide labeled Organization Views would have anything to do with personal views plus I thought the recommendation was only to use import before going live with that option. 

Ok, checked out the mentioned ticket.  It was not about exporting/importing personal views.  It was that the Organization Views created via the Web Employee Portal did not export, only the ones created from the Astea Browser.

The problem description was:

The Application Setup Guide module has 2 issues when exporting/import Organization Views…

1) Organizational views created within the WEB PORTAL – BOBA (stored in the cp_application_views table) are NOT exported. Only Organizational views created within Astea Browser (stored in the application_views table) are exported.

2) Organizational views created within Astea Browser that have spaces in their names, give and error when imported into a DB that does not yet have that same view. The error is “Execute Macro 'Save' failed.reason: Symbols such as $, %, =, --, >, <, comma, semicolon, space, apostrophe and double quotation are invalid in this key field 'order_locator_scroller_qbe_order_locator_scroller_qbe_Unfiltered View'. -(API Error)”

For this reason, they developed two different organizational view exports; one for Organization Views and the other for Web Views.  This was fixed with the v15.4 SU4 release.

To confirm, I did an export for Web Views and it still only exported Organization Views, no personal views though they existed.

Phil is correct. The fix corrected import/export bug for Web interface views and included in 15.4 SU4 but that affects only organization views.