Simple add or remove email app

[Anonymous]

Hi All,

I am looking to build a simple app that adds or removes a users email address to a sharepoint list.

I have been able to build something that adds the user's email address, either through a form submission or a patch. It's the removal part where it gets a bit challenging.

Any advice here would be highly appreciated.

Kind regards,

[RusselThomas]

Hi @Anonymous ,

You can look at the Remove() and RemoveIf() function, this should help you remove a row from the SPO list based on a condition - many different ways to implement depending on how you're implementing it on the screen.

i.e. if you have a gallery with all your SPO items, you can add a Trash icon to the gallery row and just set it to 

Remove(Source, ThisItem)

Kind regards,

RT

[Anonymous]

Thanks Russel, I'm literally just looking to have the app almost have two very basic buttons that are just add and remove. Is this possible or do I need something like a gallery? I guess the issue with a gallery is that as a user you would then see everyone else who is on the sharepoint list?

[RusselThomas · Accepted solution]

Hi @Anonymous ,

If you're just adding their User().Mail into an emailColumn, you can just as easily remove the row of data using the same value as a condition.  No need to show them all the rows if this action is isolated to their user context.

RemoveIf(Source, emailColumn=User().Email)

You might get a delegation warning using User().Email in a condition like that, especially in Filter functions (I'm not sure how fussy the RemoveIf() function is) - but if you see a blue squiggly line under the formula, or you see a delegation warning on it, you can use your App OnStart: property to set up a global variable you can use throughout your app for functions like this.  Something like the below should be fine; 

Set(gvarUserEmail, User().Email)

You can then use the variable in the condition as follows;

RemoveIf(Source, emailColumn=gvarUserEmail)

This dodges the delegation issue by passing in a string into the query instead of a function. 

Do note that RemoveIf() will remove ALL rows where that condition is true, so if you have multiple rows with the same email you may want to add some conditions.

Kind regards,

Russel

[Anonymous]

This works perfectly thank you!! Only thing I would ask is how would you allow for a pop up to show that the removal has been successful? On the adding I can do it through the onsuccess option, but unsure for the removal?

[RusselThomas]

Hi @Anonymous ,

So RemoveIf() is slightly different to Patch or SubmitForm which return the record they insert - RemoveIf() instead returns the resulting dataset after the remove has happened.

If it can't find the record you want to to remove, you'll just get the whole dataset back without errors, so you also can't rely on Errors() because you won't get any unless there an actual connection error with the source or something.

This makes it difficult to know if a removal actually took place without doing another LookUp or Filter afterwards to confirm the data is no longer there.

You can just trust the process and use the Notify() function to say "Successful" - or you can first do a lookup for the data and if it comes back blank, then do the Notify.  Something like this;

RemoveIf(source, condition);
If(IsEmpty(Filter(source, condition)), 
   Notify( "Removed", NotificationType.Success),
   Notify( "There was an error removing the item", NotificationType.Warning)
)

Hope this helps,

RT

[Anonymous]

Amazing thank you!!