@David_MA thanks for posting that! I had no idea the modified column could be changed. I just tested it a few times and it appears to work. (The guide could've given the text format to copy instead of just photos.)
I wouldn't necessarily be afraid to use it. I just tested it a few times and seems fine to me.
There is another column "SMLastModifiedDate" that is System Modified Date and it will change whenever you modify the item, even if the "Modified" field is manually changed.
So it's not like you are secretly hacking and tricking the system. The "SMLastModifiedDate" will continually update.
I just made an example, it seemed to work just fine. Basically, you update the item with a HTTP request. But before the HTTP Request, you use a Get Item to get the info and current Modified time. Then you put that in the HTTP request to basically updated the Modified time with it's current Modified time.
So in my example I was updating the Title field, @Wompwoh you would update your Count columns or whatever.
Get Item - Update Item with HTTP Request using it's own Modified time to update the Modified time and remain the same.
Here is the text in the body - these can be tricky and spacing can cause things to error, so be mindful of how you format your HTTP request.
{
"formValues": [
{
"FieldName": "Title",
"FieldValue": "Account Main"
},
{
"FieldName": "AgentName",
"FieldValue": "Susan"
},
{
"FieldName": "Modified",
"FieldValue": "@{outputs('Get_item_to_update')?['body/Modified']}"
}
],
"bNewDocumentUpdate": true,
"datesInUTC": true
}
The part at the bottom datesInUTC is important because you don't have to format the modified time. If you don't do that then you will have to format it in the local method which is very odd considering all other date times want UTC, but the Modified wants local.
Anyways, good luck, I would be confident using this method. But I just learned it 30 minutes ago lol, so maybe it does something else I'm not aware.
