Okay, I have another question. Why it is working when I create a new unit of work scope?
I just want to add aggregate root-value object relation as batch. So you can see that inside the profile list, I have multiple profiles and its edge definitions. I expect that when I send the request, it should create 3 edge definitions record for each profile (total 9 edge definition records), because I have the FK-PK relationship between Profile and EdgeDefinition with OwnsMany relation which can be used for value objects. In logs, somehow it changes the foreign key property to latest one, but I expect that it should create different edge definition object not changing the FK.
And also, when I try to save it immediately with InsertAsync method, I got an exception
It seems to me there is a transactional issue. I expect that it should create one profile and 3 edge definitions each loop. Should we expect that value object can be changed like that while sending the aggregate root as batch? I expect that it should create aggregate - value object relation without changing anything.
It should create 3 edge definitions for each profile. You should see 9 different edge definitions. I can only see the edge definitions which are belong to one profile which is starting with Guid “BCF”. If you try the working code, you see the difference
I've sent it
Okay, it works. Thank you
I've sent it
It appears that it is a problem with the newest version. We haven't experienced such an issue so far. Btw, I've tried the code above and it works. If I understand correctly, we MUST enable the redis with tiered applications after v8.0, right?
I am running AuthServer, HttpApi.Host and Web.Host
I've sent it
Is using the client credentials flow suggested if I want to use the remote service in the background job?
