Reputation: 319
I'm creating a solution which will be released as a managed solution for Dynamics CRM Online. However, the customer will need to put information in when installing the managed solution to allow interaction with outside services. For example, when you install the LinkedIn solution, you need to add your log in information to allow the CRM to access your LinkedIn account.
How do I add these parameters to the a solution, and then allow the customer to update them if they change?
Cheers
Edit: To add to my query and following the answer below. To make sure the process is correct in my head.
Option 1. I will create a custom entity for storing key/value, or username/password combination. I would then create a customisation page for the solution using html web resource, which when submitted, javascript would create a single record to hold those values.
I then need to link every record that needs the values stored in the custom record - I'm not sure how this would be done without editing a workflow after the storage record has been created, to link each normal record to the storage one.
Option 2. Create an xml web resource that stores the values. Create the html/javascript resources to update this using the configuration page. I can then use a javascript function to obtain that data when the custom entity is created, perhaps to populate hidden fields for storage and use behind the scenes. I can't find any tutorials on getting started with using xml in this way - can you point me in the right direction?
Upvotes: 0
Views: 873
Reputation: 968
I typically create a "Configuration" entity that has Name/Value attributes. This is also useful when you have Dev/Test/Prod environments that require different configs (e.g. URLs, credentials, etc).
Another approach is to using Plug-in configurations or Web Resources to store that type of information. The Plug-in configuration is pretty straightforward if you can have the customer use the Plug-in Registration tool to modify the value.
Upvotes: 1