Updateif button for all gallery items

[RMDNA]

Hi all, just a couple questions about gallery interactions.

Question 1:

I have a bunch of items in a gallery from one of my collections. Each item has a button with an updateif OnSelect to update that record's status. What I'd like to do is add another button, outside the gallery, that runs the same operation for all items currently in the gallery. 

Data source is Dataverse, Gallery is galWeeklyTimeEntries, Collection is ColWeeklyTimeEntries, button OnSelect is:

UpdateIf('Project Approval', 'Time Entry'.'GUID' in ThisItem.AllGUIDs, {'Record Stage': 'Record Stage (Project Approval)'.Approved});

The gallery items are aggregations of individual entries, so the button is taking all the GUIDs for all those entries and changing their status. I thought about changing ThisItem.AllGUID to galWeeklyTimeEntries.AllGUID, but that apparently doesn't reference the individual items.

Question 2:

If that's possible, I'd also like the option to "Approve All", but only for items that have been checked via a checkbox in the gallery. Also doable?

Thanks!

[RandyHayes]

@RMDNA 

If that is the case, it means the entire formula is returns to something wrong.  What action are you putting this on?  My assumption was you have this on an OnSelect of a button or something?

[RMDNA]

Correct, it's a standard button OnSelect.

[RandyHayes]

@RMDNA 

Out of curiosity, we also mentioned the button inside the gallery that updates only the records associated with that grouped project...is that working properly?

Also, I don't believe the _item.GUID is quite right.  It should be whatever column in your record that has the record identifier in it.

If you remove that column and value from the formula (the 'Project Approval': _item.GUID, part), does the error go away?  It obviously would not work, but I am curious if it is complaining about that.

[RMDNA]

@RandyHayes

1. If I switch the in-gallery formula from UpdateIf to the Patch formula you provided, I get the same error we're working with now.

2. For _item.GUID being off: to test, I created a data table with the Items property Ungroup(Filter(galWeeklyTimeEntries_2.AllItems, cbCheckbox_2.Value), "Other"). As a column, both ThisItem.GUID and ThisItem.msdyn_TimeEntry.'Time Entry' (the backend name) show the correct values. Using either in Patch() gives the same error.

3. I removed that component, and although the formula itself now is valid, I get a red error circle that says "msdyn_name: Field 'msdyn_name' is required." Very strange, since Msdyn_name is the field name for the user attached to the time entry, and I have no idea why it would be necessary, or where to put it.

[RandyHayes]

@RMDNA 

There's something about the identifier!  If you are getting that error, then the patch is not matching the identifier but instead is trying to create a new record - to which, it is most likely then warning that a required column is missing.

When you Patch with a ForAll, if you don't supply the identifier, it will create new records (and thus need all the detail).  If you supply the proper identifier, then it will match the record that exists and patch the supplied column values.

So, I'm thinking we're still off on the identity.  I don't work with Dataverse as much as I should to know all the ins and outs on it.  But I know the function works properly as I did vet that before suggesting for you.

For me I had a TestEntity table (that was pluralized to TestEntities). 

My formula was :

Patch(TestEntities,
    ForAll(Ungroup(Gallery71.AllItems, "_recs") As _item,
        {TestEntity: _item.cr444_testentityid,
         Status: Radio4.Selected.Value
        }
    )
)

The Items for the Gallery were identical to what I had sent in regard to the Grouping.  The only difference was with the Status where I had that in a Radio control just so I could set it back and forth to test.

In the "in gallery" button, the formula was:

Patch(TestEntities,
    ForAll(ThisItem._recs As _item,
        {TestEntity: _item.cr444_testentityid,
         Status: Radio4.Selected.Value
        }
    )
)

See if you can spot anything significant to your scenario.