Word template creation for an agreement entity RRS feed

  • Question

  • Our company is trying to make a smart quote/agreement document creation feature with CRM data, using the new word template abilities in Dynamics CRM 2016. The aim is our personnel should be able to create a quote with as little as hassle as possible and a lot of data gets automatically filled in with existing crm data.

    So far we have created a new entity for this that also use lookup data from the account and contact entities and N:1 relationship data that goes in to the word template.

    BUT - For this quote/agreement entity we would also like some kind of functionality like if "Service A" is chosen for the customer then "Legal text 1" is put in to the word agreement document template and if "Service B" is chosen, then "Legal text 2" is put in the template and so on.

    Someone suggested this could be done out of the box with the new template abilities, but we are struggling on exactly how to achieve it. I suppose it could be possible to use lookup to some entity containing the legal information.

    But we really would just like to have like an optionset, so that you simply choose an option in the agreement-entity and a specific text appears.

    Is that at all possible? Any input is appreciated. Thanks in advance.

    Wednesday, June 8, 2016 8:52 AM

All replies

  • The best way would be to build a new lookup entity that would contain a field for Service names, and legal text.  Select Service A from this entity, then use the N:1 lookup to pull the Legal text on the report.  This would be the most flexible way and allow you to add new services that require new legal text.

    You 'could' do it with an Optionset and some custom workflow or js code?  You would need 2 new fields.

    1. Optionset with Service A and B

    2. Multiline Text field to store Legal text

    Then you would build a workflow or JS that monitored the changes to Optionset and would put Legal Text 1 or 2 into the new Multiline field.  This would work, but would require code/workflow changes each time you had a new option or legal text.

    Wednesday, June 8, 2016 1:31 PM