web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Dataverse (MDA): Sudde...
Power Apps
Answered

Dataverse (MDA): Suddenly cannot change custom activity date fields to "date only"

(1) ShareShare
ReportReport
Posted on by 48
I'm working on a model driven app which uses a lot of different custom activity tables, in a custom solution. Up until this week, I was able to change the fields "scheduledStart" and "scheduledEnd" from "date and time" to "date only". However, as of this week, that is not possible.
 
I have five custom activity tables from before this week, where these two columns are correct (date only). When I try to do this with the remaining custom activity tables, I get the following error:

"cannot modify the behavior if canmodifybahavior is set to false for OOB date time attributes of a custom entity"
 
I cannot see any updates in Dataverse or Power Apps that would explain this. Has anoyone else experienced this? Or does any of you know of a solution? There is no mention of "canmodifybahavior" anywhere that I can find. I've tried looking at the documentation, but the only thing I can find seems to say that I need to import the solution with modification enabled(?). But it worked up until this week, so that doesn't really make sense to me. And I don't want to do that until I know this is the correct path. 
I have the same question (0)
  • Verified answer
    MariusHT Profile Picture
    48 on at
    OK, so this is embarrasing - I once again tried using the classic experience (per this walkthrough, as I've done before). I don't get an error using the classical experience, but neither does it update the field to "date only" in the classic experience fields list. It still shows as "date and time".
     
    However, when I switched back to the modern experience, the field was correctly set to "date only". It seems to be a bug in both the classic and modern experience(?).
     
    Changing the column in the modern experience still throws the error mentioned above. So a workaround seems to be to use the classic experience for this particular function.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 342 Most Valuable Professional

#2
11manish Profile Picture

11manish 234

#3
Valantis Profile Picture

Valantis 187

Last 30 days Overall leaderboard