Update property on custom DataCard from a Collection not visible

[Anonymous]

I am trying to create an edit screen where a user has the ability to edit an individual record of a Collection prior to Patching the entire Collection to the Common Data Service.

For some reason, the Update field of my DataCards is not showing in the EditForm properties. Because of this, I am unable to get the SubmitForm() function to work. I have successfully accomplished creatign an edit screen in the past, and the only difference seems to be the lack of Update fields on my DataCards:

Has anyone run into this? I thought it may be a new update from Microsoft that removed the Update field, but I can't find any documentation.

Thanks in advance for your help!

[PauloRech]

Microsoft has took out the Microsoft Access with web forms, telling Power Apps should be used instead Access...
But PowerApps still has a lot of confused routines, and a lot of easy functions that do not works...

 When will Microsoft work to provide a good and realy easy enterprise solution?

I miss Microsoft Access!

[Boneckrh19]

I think if you are editing collections you have to(?) use a collect/patch/updateif function, instead of submitform. It certainly seems ridiculous to me that collections are regarded as proper datasources only sometimes. I have an idea out there requesting that collections behave like any other datasource if you would like to vote.

https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Allow-Collections-to-be-used-as-a-DataSource-in... 

[TickboxPhil]

I just found this mysterious "missing Update" on cards happened when I changed the Primary key on SQL table, from an auto-increment numeric() ID to a unique varchar(). Even after waiting a while (I've noticed some backend changes take a while to take effect in PA, even after hitting the Connector Refresh successfully!), adding the new PK field back as a brand new Card leaves the Update off it... grrrr!! Nothing seems to get it back, as confirmed here so far.

However, If I delete the Form and create another, the PK varchar() field is fine and Card has the Update! So now have to go back to renaming all the other new objects with decent naming conventions and re-wiring all the dropdowns etc... grrrr2!!

Maybe it's because PA has automatically generated all the patch statements behind the scenes, and the PK change messes it up. Although everything else works fine, just not the actual field. Just be careful not to change the backend PK! But MS should fix this to regenerate the PK Card, and save all this hassle. Would be interesting to see where else the Update drops off, where no PK change was made.

[Anonymous]

I just created my account to thank you and get your answer a thumb's up, I had the exact same problem and can't figure it out until I saw your post.

[TickboxPhil]

Thanks @Anonymous - and to @PauloRech ... I too miss Access (not sad to leave VBA but compared to PA it is immensely powerful!) and WinForms C#... and although PA is still catching up, it is improving daily and has potential to wipe the floor, so sticking with it for now and hope they sort out Patch/UpdateIf etc!

[ivanmezev]

@TickboxPhil, explaining this you saved my life. I had exactly the same problem and was trying for ours to fix it.

Thanks

[aboehm]

I have the exact opposite of this issue, but the root cause seems to be the same.

I updated my data source (SharePoint), so that a column becomes a additional field to a lookup column, which makes the column read-only.

When I add this column in a PA EditForm, the corresponding DataCard is correctly created with DisplayMode.View, so the users can't change the value, but they see what is in this additional field of the lookup column.

The problem here is that this DataCard still has this update property filled with the default value of the record.

So when I use SubmitForm() the underlying Patch tries to modify this read-only column and the data source errors out with the message, that this column is read-only!

I can't find any way to remove the update property except creating a custom DataCard from scratch.

Would be nice to have a property on DataCards where you can define if the Update property is actually being used or ignored. Then PA can be changed to always show the update property on DataCards, so no one has to mess with this "smart" logic behind the scenes.