Editing templates in system areas – UAC Data Virtualization pitfall

When editing the example templates that ship with RPE or OOTB templates that ship with other products you might find that your changes are not visible in the point product and not even in Windows Explorer.

This is happening because of UAC data virtualization which basically means that Windows stores these files in a different location and only shows them to your user as being in the system folder.while all other user accounts will not “see” them.

Typically this location is %LOCALAPPDATA%\VirtualStore  You can paste this path AS IS in Windows Explorer to see if you have any files there.

See below the content of this folder after I edit the doorsData.dta example that ships with RPE without running Document Studio as administrator:


UAC data virtualization shows different solutions to this but what I usually do is edit the files in a different location ( the D:\ drive ) and then copy the files in the system area. This approach has the added advantage that if I make a mistake while editing the template I do not destroy the version of the template that is in production.


The copy operation will run with admin privileges which ensures that the file will be copied in the actual folder and not in the Virtualization Store.




Author: Dragos Cojocari

Architect for Rational Publishing Engine

7 thoughts on “Editing templates in system areas – UAC Data Virtualization pitfall”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s