❏ Limitation of fields available for "Use values from existing fields" when creating dropdown fields
- Assigned to
-
Martin L.
- Notes
-
Further to the video below, the "Use values from existing fields" option for populating the values in dropdown fields appears to be limited to only managed fields. Ideally I would like access to all fields available in other forms (including hard coded fields) to populated values in manage dropdown fields.
As discussed earlier, the Proceeding Stage Field in Dispute Document Form is fixed. that filed is not managed by Meta Field.
Hence, The Proceeding Stage Field will be not available in Use Value Drop down.
I have told that the 5 fixed category we fixed in database and it just showing only on Dispute Document Form as Fixed.
Now, You want that field in Use Value list so we need to again change and make the miscellaneous of Proceeding Stage and add those 5 categories in to the list and then you can get option of miscellaneous list while you create new meta field.
Please confirm.
Ok. Understood. But why are fixed/hard coded fields inaccessible through the Data/Value Field dropdown? Pulling the values for other fields won't affect the fixed fields or values in any way, so I don't understand why access is restricted.
Thanks,
Morgan
We are allowing hard coded fields in Use Value Drop down. But, the Proceeding Stage and Document Type those 2 field are fixed which we set up through programming in dispute document form.
These 2 fields are not binding through Meta Field Page.
Hence, You noticed that Proceeding Stage and Document Types field you can see horizontally line. Generally, Meta Field always display vertically.
Proceeding stage and Document Type, These 2 fields we developed manually as fixed in Dispute Document Form which we already discussed with Melisa.
For more clarification, These 2 fields data binding is not manageable through Meta Field.
Document Type : Binding Data from Document Content Types Page (Except all Masters)
Proceeding Stage : 5 Fixed Categories (Legal Analytics Grouping Page).
The above 2 fields data binding are not manageable through meta field page. Hence, Those 2 field we set fixed programmatic in page.
The only solution is we need to create miscellaneous list for 5 fixed legal categories and do this change on Dispute Document Form.
Like Morgan, I would expect that all the fields on a master list form, hard coded or managed would be available to select in the 'data values' field, including:
Why is this not possible?
Mel
The above 2 fields are not managed through Meta Field. How can we bind Document Types and Proceeding Stage data from Meta Field ? because those data are not pulling from any miscellaneous or master form. Those data are pulling from document content types.
That's why we have already discussed this thing ago while we set those 3 field in dispute document form.
Those 2 field data are binding by query in particular Dispute Document Page.
If Morgan wants Proceeding Stage field then we need to create miscellaneous list of proceeding stage and add those 5 fixed category.
And then it will be easy to create new field and select option from miscellaneous list.
Hope you get my point.
I am available now to discuss this point on skype call.
Why do the fields listed in the Data/Value Field dropdown need to be pulled from the miscellaneous or master forms? Pulling the data to populate dropdown in other fields will have no impact of the pulled values or fields, so even if the values are fixed, why can't we make these available in other fields?
Also, the options in Data/Value Field dropdown are more limited than what you've described. For example, for Administering Institutions there are no fields available in the Data/Value Field dropdown:
From what you've described above, all these fields should be available:
Thanks,
Morgan
Those fields are not dropdown or searchable dropdown field.
All fields are textbox and those values are not associated with any list.
We should talk this thing on monday staus call so i can explain you.
Ok. That makes sense about the type of fields. However, yes, let's discuss how to deal with this on Monday, because we'll need to come up with a solution to this and the multi-select issue.
Thanks,
Morgan
As discussed per yesterday call, We have removed fixed Proceeding Stage field from Dispute Document.
We have made this field through Meta Field page as hard coded field using Proceeding Stage Miscellaneous list.
Following are screenshot for your reference.
1) Remove fixed proceeding stage field
2) Render Proceeding Stage field through Meta Field page and hard coded
3) You can use Proceeding Stage List Miscellaneous List
We did this change in both rebuild.islg and rebuilddemo.islg.
Morgan
Further to the screenshot below, I still can't select "Proceeding Stage" in the Data/Value Field dropdown when creating a field in Legal Analytics:
With the change above, shouldn't I be seeing this now?
Morgan
My Apologies..I haven't checked this thing.. Might be some minor thing will pending. We will resolve and deploy by tomorrow.
After discussing the issue above with
Morgan
The issue of Proceeding Stage field in Data Value dropdown is resolved in both rebuild.islg and rebuilddemo.islg.
The above mentioned thing "Related People" will talk today and then will start work on it.
Mel
Thanks,
Morgan
The "Use values for existing fields" are working now. However, further to the video below, there now appears to be an unnecessary restriction on making these dependent fields:
Could you please remove this restriction.
Thanks,
Morgan
We understood your concern. Now, there are 2 scenarios is happened in when make meta field through "Use values from existing fields" option.
1) First Scenario :
When user select any reference field except All (For example, All Dispute, All Dispute Document) then it will always work as dependent field.
Like, You are going to make Claimant Organization Field. Hence, you will do following steps
1) Select Claimant Person in Reference field
2) Select Organization from Data Value Field.
Claimant Organization will be automatically dependent on Claimant Person. Hence, the Dependent checkbox is disabled and we discussed same thing with Melisa.
2 Second Scenario :
But, Now When you Select All Dispute, All Dispute Document etc.. from reference filed that time we need to enable dependent field checkbox and you can make any parent field.
We need to do 2 separate conditions for same use value option. We can able to do this change but it will require to put one more condition to separate All thing and normal reference meta field.
It will require 1.5 day work with one developer with testing. Let me know.
Thanks,
Morgan
As discussed on Wednesday call, We have created "Related People" in Select list option.
As per following screenshot, When you will go to create new meta field and select "Related People" then data of People master will be narrow down and fetch the only specific dispute related people data from all people related fields in dispute master.
We have deployed this change on both rebuild.islg and rebuilddemo.islg
However, I'll wait until we have the user stories written concerning the option to filter the selected list(s) by entries associated with a particular Dispute form and the multi-select option for the "Use values for existing fields" before moving this to-do for Fix Later.
Also,
Thanks,
Morgan
When creating a field that uses values from an existing field, the field selected as the reference field in essence becomes the parent. The values of your field are "dependent" on your selection in the reference field.
This is not the case when using 'All <content type>' as a reference, and therefor the dependent relationship is available.
Hopefully this makes sense.
Mel
Ok, I understand the relationship between the reference field and data/value field, but I still don't understand why that should prevent me from making the new field dependent on another field within the same form. We're only using the reference field and data/value field to populate the dropdown options, but it should not affect how data entered into that field is dependent on entering data into other parts of the form.
Morgan
As per my above comment, we are able to enable the depended checkbox in meta field page while any user select All Dispute, Dispute Document, People etc.. and hence we need to do following change.
When you Select All Dispute, All Dispute Document etc.. from reference filed that time we need to enable dependent field checkbox and you can make any parent field.
We need to do 2 separate conditions for same use value option selection.
1) While select any Meta Field in Reference field drop down then need to disable the dependent checkbox
2) While select All Dispute, All Dispute Document etc.. that time need to enable the dependent checkbox
It will require 1.5 day work with one developer with testing.
Please confirm.
Morgan
Further to our discussion this morning, to clean up this to-do, could you please post a comment with the links to the user stories dealing with the following issues:
Morgan
Please find the user stories below:
https://industrialagency.tpondemand.com/entity/16324-improvement-filter-values-by-dispute
Morgan