L2vpn-Service is giving the full path instead of the feild  name : /l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-servicegetSchema api sending the full path url instead of field name and please find the attached screen shot 
There are few more changes also need confirmation in VPN service is these are expected chnages and been added as part of some modal changes ? 1. New Leaf node is been added :name : vpn-type {kind: "leaf", name: "vpn-type", qname: "l2vpn-ntw:vpn-type", info: {string: "Service type."},}deps: info: {string: "Service type."}kind: "leaf"name: "vpn-type"qname: "l2vpn-ntw:vpn-type"type: {namespace: "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw", name: "t551244651"}2. Leaf been removed in M3 {kind: "leaf", name: "vpn-svc-type", qname: "l2vpn-ntw:vpn-svc-type", info: {string: "Service type."},}access: {create: true, read: true, update: true, delete: true, execute: false}info: {string: "Service type."}kind: "leaf"name: "vpn-svc-type"qname: "l2vpn-ntw:vpn-svc-type"type: {namespace: "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw", name: "t2237769791"}name: "t2237769791"namespace: "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw". Hi Kirandeep,Regarding vpn-type and vpn-svc-type : The IETF-L2NM models have been completely refactored due to updating to the latest draft in M2. vpn-svc-type was changed to vpn-type during this update. Please refer to the M2 Model and Payload changes page for more details.Regarding 'evaluate_when_entries' attribute : As per the JSON RPC documentation : The evaluate_when_entries param signals that schema entries should be included in the schema even though their "when" or "tailf:display-when" statements evaluate to false, i.e. instead a boolean evaluated_when_entry param is added to these schema entries. i will check more on this attribute and update you.Regards,Nishad Subair.Hey Nishand, can you please update regarding the new attribute added and name is not coming correctly. Thanks KirandeepHi Kirandeep,We will check this and update you.Regards,Nishad SubairHi Kirandeep,We have raised a RT with the NSO platform team and will let you know once we hear anything from them.Regards,Nishad Subair.Hi Kirandeep,RT has been resolved and the fix is available in the NSO build : 6.1_230206.110843541.f67ad1e6cc9d.Please verify.Thanks And Regards,Nishad Subair.