[Bug]: A portal cannot have a List ProfileProperty identical to another portal

[skamphuis]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

In an installation with multiple portals, different portals can't have a profile property with the same name and values. If you enter a list value, you will get a popup saying it has been added, but it's not:

This is caused by Unique constraints on the Lsts table, not containing the PortalId column.

Steps to reproduce?

1. Create a profile prop of type list (FavoriteColor)
2. give it a few values (Red: 1, Green: 2, Blue: 3)
3. create a new portal in the same installation
4. Create a profile prop of type list (FavoriteColor) in the new portal
5. Try to give it a value you already used in the other portal (Red: 1)

Current Behavior

If you enter a list value, you will get a popup saying it has been added, but it's not:

Expected Behavior

The value should be added.

Relevant log output

none

Anything else?

I'm working on a fix.

Affected Versions

9.13.7 (alpha)

What browsers are you seeing the problem on?

Firefox, Chrome, Safari, Microsoft Edge

Code of Conduct

• I agree to follow this project's Code of Conduct