Hi, first time questioner. I did a bunch of searching but seemed to come up with nothing. Pardon if I mess up some terminology as I am a product manager, not a developer. I'm trying to discern the feasibility of a feature before 1- promising it to users and 2- asking someone to develop it.
I would like to create sets of related fields, and then allow users to add multiples of these sets (example below). I realize I could do this with other entities and then relate them to a case. However the relationship of these fields only applies within the context of this single case so it seems pointless to create entities for this purpose. This would risk someone else modifying the entity in the future and having that change cascade to previous cases where the entity was referenced.
Example:
Let's say I have a case system where I track complaints from users that call in. Users often have a single complaint, but sometimes they have many. I'd like to be able to track these complaints in a simple manner that doesn't overly tax the Service Rep.
Complaint (Free text field)
Complaint type (dropdown single-select field)
Complaint sub-type (dropdown single-select field)
Complaint resolution (dropdown single-select field)
Complaint resolution notes (free text)
If the user has a second complaint the Service Rep can hit some button to add all of the above fields again and receive in the UI (or similar):
Complaint 2 (Free text field)
Complaint type 2 (dropdown single-select field)
Complaint sub-type 2 (dropdown single-select field)
Complaint resolution 2 (dropdown single-select field)
Complaint resolution notes 2 (free text)
The user should be able to add n number of these sets.
To drive the point home, these should not be referenced entities since the "text, type, sub-type, resolution, resolution text combo" only applies in the context of this particular case. No one would ever be opening a new case and linking it to that exact set of values; nor would I want them too as that would potentially allow them to change them and therefore ruin the integrity of the data for the previous case.
Thoughts? Does Dynamics allow for this?
Chris
