How to differentiate from get_Schema API response to load leafref key in different cases: Previously prov-ui editor renders any leafref as a text field with validation that user entered data exists (default behavior ).Now we have different cases to render on prov-ui editor ,As prov-ui editor is dynamic and generic way to load the modal we need help in identify the solution to differentiate between two cases.some use cases prov-ui need to add a custom dropdown as a special case e.g in case of VPN-Profiles.Based on initial analysis To handle these cases generically we have added a check based on--> IN case, If we have ( is_leafref = true , kind= key ) without any value we load it as a custom drop-down--> IN case, If we have is_leafref = true , kind= key and has value =ct-logging we load it as text field with validation that user entered ( default behavior).Just want to confirm is this valid check and enough to handle for all the case or is there a way we can differentiate between two to handle both cases except adding these checks.NOTE: added the screen shot for these KEY response form get_schema JSON RPC call.
Hi Kirandeep,In a scenario, where the leafref points to value A,B,C and D.If you have a model without any value field, then yes the drop down list would be correct.If the model shows a value chosen from the leafref then yes, the textbox/text-field would be the right choice to populate the value.Let me know if this helps?hey janaki, Thanks for confirming, so we can go head and add that check based on value felid we populate the dropdown and text for leafref pointsQuick question - how will you be populating the drop down? What field will be used?In case of Leafref as kind key we are using custom modal select field to populate the dropdown on selection we do validate by calling method: "exists" in JSON RPC call.Okay, thank you. Please let me know if your query is answered and if I may close this ticket.yes we can close this ticket got the confirmation needed Customer requested feedback wit design question. Feedback/Clarification was provided.