There seems to be a bug with the Set as Primary button on an Opportunity.
Here are the steps to produce:
- Create an Opportunity
- Create a Project Quote. Ensure you set its Opportunity ID to be the Opportunity ID of the Opportunity we created in step 1
- Create another Project Quote and also set its Opportunity ID to be the Opportunity ID of the Opportunity we created in step 1
- Use some mechanism to fetch both project quotes, I just use Postman. Note their LastModifiedDateTime’s…
- Click the Set as Primary button on the Opportunity for the Project Quote that is not presently the Primary one (we specifically choose this Project Quote as this is a data change and should -- at least, in theory -- update the LastModifiedDateTime of the Project Quotes)
- Repeat step 4. Note both of their LastModifiedDateTimes remain unchanged.
Is this a known bug or planned to be fixed? Our company uses the LastModifiedDateTimes for DB syncs and this is a major problem for us. I’m aware of workarounds and plan to address the problem myself with a customization project solution. I just wanted to bring it to your attention.
Thanks all!