
Hello! My company builds warehouses, so there are a lot of details that we collect from our opportunities. Potentially hundreds of data points are supplied by the customer, relating to employee scheduling, growth, temperatures, receiving, shipping and so on. Sometimes we consider multiple site locations, so there will be sets of facts that need to be grouped together.
To put it informally, I want a salesperson to be able to click "Add Fact Sheet", be presented with a list of questions, and then save those answers. But I want to have each question as an entity so that I can add properties to the entity, such as "this is a critical question" and ordinals and grouping. I want to avoid creating an entity type with one field per data point that we need to collect.
I'm imaging an entity design that has:
I'm planning to build a simple forms-over-data app in Power Apps to allow the team to interact with the data.
What I want to avoid, and I'm not sure how, is that when creating or editing an Opportunity Fact Sheet, I'd like the form to present all of the questions (the Opportunity Fact Types) showing the current answer (the Fact) if the data was supplied already, and an empty input field if it hasn't been entered. And, most importantly, I want to avoid requiring the user to click an Add button for each Fact they want to supply.
Any advice? Is there a better way to do this?
Hi Alex,
Do you have a license for Dynamics 365 Customer Service?
If so, the knowledge articles function of Customer Service can meet your needs, and it can be used in Sales Hub.
Please refer to docs.microsoft.com/.../search-knowledge-articles-csh