-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem with execute <entity-find-one/> on ViewEntity #101
Comments
For case 1, after scrutinize the EntityFindBase I find that:
I've tried to change the method
This fixed the issue that use entity-find-one without any field-map. However, I don't know if this change will have any side-effect or not. About the case 2, I can't reproduce the issue. |
Would you pull the latest code and try this again? I am unable to reproduce the error. If I understand correctly this error should be seen by just going to: http://localhost:8080/apps/hmadmin/User/EditUser?partyId=EX_JOHN_DOE That screen and the populated form are rendering fine for me now with the single PK for the view-entity entity-find-one. Let me know if there is something different that needs to be done to reproduce this issue. The EntityFindBase code, and lots of code related to it, has been reviewed and updated quite a bit (mostly for performance/efficiency), and while it is somewhat complex and messy to run faster it should all be working now. |
This issue not happen with newest code. It has been fixed in commit 2e6eaff. |
Scenario 1:
In screen: component/SimpleScreens/User/EditUser (call via url /apps/PopcAdmin/User/EditUser)
record ID is existing, but record value is empty (checked via debug)
After checking following code:
into new one:
it works as expected
Scenario 2:
In screen: component/SimpleScreens/Supplier/
party.pseudoId
is nullI got problem with scenario 2 once and I can't replicate it.
I guess there's something wrong with entity-find-one with viewentity with cache.
The text was updated successfully, but these errors were encountered: