“Could not find a property named modifiedon”
If you’ve worked with Power Automate flows or JavaScript in Microsoft Dataverse, you may have encountered errors indicating that a specific attribute (column) cannot be found. This usually means that the column you are trying to reference either does not exist in the table or its logical (schema) name is not an exact match.
Below are some common reasons — and how to fix them:
Case Sensitivity of Property Names
Dataverse property names are case-sensitive. While ‘ModifiedOn’ is the standard logical name for the “last modified date” field, you must ensure that the casing in your Power Automate flow or script matches the exact schema name — e.g., ModifiedOn (correct) vs modifiedon (incorrect, unless your environment uses that specific casing).
Incorrect Logical (Schema) Name
The display name of a field (e.g., “Modified On”) in the user interface may differ from its logical name in Dataverse. Even if it appears the same in the UI, the backend schema may store it differently — for example, modifiedon is the standard logical name for the last modified date, but custom fields or managed solutions could have variations. Always verify the exact logical name in Dataverse table settings before referencing it.
Work around
To avoid such errors, use the Dataverse advanced find or Dataverse tables to copy the exact logical name of the column and paste it directly into your Power Automate or JavaScript code. This ensures accuracy and reduces troubleshooting time.
