Matching profile does not follow edited scope of segment
Found in
EPiServer.Profiles.Client 1.6.0
Fixed in
EPiServer.Profiles.Client 1.6.0
Created
Aug 14, 2018
Updated
Sep 19, 2018
Description
econdition:
User with account admin@example.com is in sinhscope, not in scope1
Steps to reproduce
- Create a segment with a matching profile 0 with scope1 with query:
POST /api/v1.0/segments/
{
"Scope": "scope1",
"SegmentManager": "HoangAnhMinh",
"ProfileQuery": "Info.Email eq admin@example.com",
"AvailableForPersonalization": true,
"Archived": true,
"FavoredBy": [
"string"],
"Name": "Segment from API2",
"Description": "Segment2"
}
- Edit the segment scope to sinhscope
Expected:
Segment is edited and the matching profile is 1.
Actual:
Matching profile is still 0.
- Note: If you create the same segment and the scope is sinhscope, the result shows that the matching profile is 1.