What is the challenge? |
We recently created a "Committed Date(s)" field to track the various dates we have committed to various customers as well as notes on the commitment. This is great but makes reporting difficult to easily see if we are at risk of any of our commitments. |
What is the impact? |
Difficulty determining at risk items and higher chance of missing a commitment. |
Describe your idea |
It would be great if AI could parse the field and then populate a Date field with the earliest committed date. |
Hi Brittani, thanks for the idea. Is the Committed Date(s) field a custom table? Also, when you say you want to populate a date field, do you mean on that same feature? So for example:
Analyze the various dates entered into the table on the feature
Find the earliest date
Add that to a different date field on the same feature
Am I understanding correctly?