I would guess that there is no association value set for each TeamMember to the JobTitles entity. Here is how you can check this:
Hope that helps,
I made a small example.
Here is the domain model
here is the microflow
Here is the JobTitle retrieve
Here is the Change action where the association is set
Hope that helps.
You made my day, great understanding of the problem, super solution.
You are the man!
Can you check read access for attribute Jobdecription in JobTitle entity?
It seems to me permissions are ok.
I think you are correct. I just had Studio Pro creating the overview pages for both the entities, added a new member by the TeamMember_Overview page, and everything works how it should.
But this brings up a different question, though. I’m building the 2 tables using a SQL query and a REST call and it seems the Mendix ‘association’ has a different meaning or, at least, different behavior, than a DB relationship, that is what I was expecting.
Based on your knowledge, is there a way to force rebuilding the ‘association values’ after populating the entity?
Thanks for your help.
Yes, I do have JobTitleId in both tables (classic relational model where TeamMembers.JobTitleID is the external key to create the relationship with JobTitle). I can create the microflow which loops through the TeamMembers table but I don’t understand how to set the association. Can you please explain it, if you don’t mind.
Thanks a lot!