Is there an existing issue for this?
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?
- Create a profile prop of type list (FavoriteColor)
- give it a few values (Red: 1, Green: 2, Blue: 3)
- create a new portal in the same installation
- Create a profile prop of type list (FavoriteColor) in the new portal
- 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
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
Is there an existing issue for this?
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?
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
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