How do I use RemoveIf equals a Dataverse lookup column?

[arpost]

I have two Dataverse tables and am wanting to delete all records in one table that have the current Form item in a lookup column. Here's some sample data:

Fees:

Fee (Number)	Model (Lookup)
10%	2021 Model
20%	2021 Model
15%	2022 Model

Model:

Model

2021 Model

2022 Model

I thought the code would be as simple as follows with the "selectedRecord" variable being the selected item in a Gallery, but I get this error:

Anyone have any ideas?

[dpoggemann]

Hi @arpost,

I just did a quick test on this in a Canvas Power App.

1. Created ComboBox that was based on Users table in Dataverse
2. Created Gallery that showed a table called Widgets and filtered "Owner" column based on the Selected item in the ComboBox Filter(Widgets,Owner=ComboBox1.Selected)
3. Created a Button called "Remove" that when selected would removeif the Owner of the widget matched the selected item in the ComboBox.  RemoveIf(Widgets,Owner=ComboBox1.Selected)

Hopefully this helps you adjust yours to work successfully.  Please Accept if answers your question or Like if helps in any way.

Thanks,

Drew

[arpost]

Hi, @dpoggemann,

Thanks for the prompt reply! Unfortunately, when I do that, all I get is an invalid type error as the Dataverse field stores the Model entry as a table (even though there's only one value), but the Combobox has a single record selected.

My first impulse was to wrap the Model lookup column reference in a FIRST function to get the first record since there should only be one, but I then still get the funky invalid type on Record, Record message.

[v-albai-msft]

Hi @arpost ,

I did a test on my side, and the formula should be like this(my second table called "Model"):

RemoveIf(Models,'Model (crea3_model)'=Gallery4.Selected.Model.'Model (crea3_model)')

So go to find the "Name" of your Model column(instead of "Display name") and then edit your formula as below.

RemoveIf(ForecastValues,'Model (crea3_model)'=selectedRecord.Model.'Model (crea3_model)')

Best regards,

Allen

[arpost]

Thanks for the reply, @v-albai-msft. One problem I'm running into is I'm using the Dataverse for Teams, and the current implementation forces the Primary Name column to be a Text field (like SharePoint does with Title, which has always been super annoying) that isn't needed for this scenario, which means I can't use the Primary Name column as it is left blank. I should add I can't redefine the primary after the fact because Microsoft doesn't allow schemas to be edited at this time. 😞

Is there any other viable workaround with this?

[dpoggemann]

Hi @arpost ,

The primary field can be a auto-number now vs. Name field...  😀

After you create the field you can change it to autonumber and make it optional which will populate.

Thanks,

Drew

[arpost]

@dpoggemann, didn't know that, but that's great news! 🎉

Do you happen to know how to get it to auto-populate for existing records when switching to auto-number?

[dpoggemann]

Sorry, don't think that is possible.  You can manually populate the values though with a number lower than the seed value (export / import)...😀

Thanks,

Drew

[v-albai-msft]

Hi @arpost ,

For existing records, you need to edit them manually. The change would only affect for new created records.

Best regards,

Allen