Kbase P15893: Looking for documentation on customization in Dynamics
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
Looking for documentation on customization in Dynamics
FACT(s) (Environment):
Dynamics 2.0a
FIX:
As a simple example:
In the following example we'll build a basic window and then create a custom version of it which will be used when a particular user logs in.
1. Open Development menu and select Customization Maintenance, as we want to base the customization on user then under the User entry add a new entry with Result Code and Result Desc of 'test'. After creating test, right click on the test entry and 'test' to the Customization Reference. Basically this is just a grouping mechanism - if you had a group of users, eg. sales, then the first entry would be sales followed by each users login which results in whichever sales user logging in getting the customization. In this example we'll just have a group with one user, using the same name.
2. Now add a user 'test'
3. In your session types for your development session (usually ICFDev), add the CustomizationTypePriority with a value of 'User' and regenerate your xml file.
4. Now relogon on as Admin (or whichever user account you were using to do the above)
5. Now build a basic container - for example just a dynsdo and a dynbrowser, with links
6. Save the container with whatever name you like. At this point we have saved the 'basic' container that will always be run for all users. If you now add 'test' to the Result Code field in the Container Builder then any changes you now make will only apply to user 'test'.
7. Thus, if you now add a viewer and the appropriate links and resave the container you can now test (note the small lines under each object in the grid now have blue lines, this is the only visual clue that you are customizing).
8. Stop/start session (re-logon does not clear all cache for this)
9. Login again as development user and run the new container - should just see the browser
10. Stop/start session adn login as 'test' - rerun the container - should now see the browser and the viewer