Add prepType to query table to edit them in same fictitious record set - #3441
Conversation
grantfitzsimmons
left a comment
There was a problem hiding this comment.
-
The Preparation Type table is sorted at the bottom rather than where it should be alphabetically. Not sure why this is.
-
How is this any different from default behavior? This is still not satisfactory & does not really make it any easier to create new prep types
This kind of thing really needs its own UI (as it has in 6) where the user doesn't feel like it's detached from the schema configuration process. It should appear like this:
Where you can add new prep types from the dialog & this should be accessible automatically when editing the preparation type picklist in the schema configuration tool.
|
@maxpatiiuk
|
Fixed. See c1b084a
We didn't use domain filter correctly. See the fix in 19666c9
This one is quite tricky. Fortunately, it's either already fixed by #3125, or needs to be fixed on that branch anyway. Basically, we need to allow for use case of creating independent records from inside of a subview, rather than just linking to existing independent records. Thus, it would be simplest to just make this PR wait till that PR is fixed
You were correct - it's simply because there are no projects in the kufish database |
Triggered by 19666c9 on branch refs/heads/issue-2754
|
If the feature in readOnly is satisfying we can merge this PR. |
grantfitzsimmons
left a comment
There was a problem hiding this comment.
@CarolineDenis looks good!
I am sad only because we cannot add new prep type records from the form, but I know it is due to the issues with independent subviews.
grantfitzsimmons
left a comment
There was a problem hiding this comment.
@CarolineDenis looks good!
I am sad only because we cannot add new prep type records from the form, but I know it is due to the issues with independent subviews.

Fixes #2754