<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Reading proplist values in a MAAPI script in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/reading-proplist-values-in-a-maapi-script/m-p/4770138#M7664</link>
    <description>&lt;P&gt;Yes, there is a &lt;FONT face="courier new,courier"&gt;private/property-list/property&lt;/FONT&gt; list in each service instance:&lt;/P&gt;
&lt;LI-CODE lang="python"&gt;In [2]: with ncs.maapi.single_read_trans('admin', 'python') as t:
   ...:     s = ncs.maagic.get_node(t, '/foo-service{bar}')
   ...:     for p in s.private.property_list.property:
   ...:         print(p.name, p.value)
   ...:
k1 v1
k2 v2&lt;/LI-CODE&gt;
&lt;DIV&gt;You can also access it in the CLI if you &lt;FONT face="courier new,courier"&gt;unhide fastmap-private&lt;/FONT&gt;.&lt;/DIV&gt;</description>
    <pubDate>Tue, 07 Feb 2023 07:16:07 GMT</pubDate>
    <dc:creator>markozagozen</dc:creator>
    <dc:date>2023-02-07T07:16:07Z</dc:date>
    <item>
      <title>Reading proplist values in a MAAPI script</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/reading-proplist-values-in-a-maapi-script/m-p/4751984#M7600</link>
      <description>&lt;P&gt;Is it possible to read the proplist values for a service inside a MAAPI script? If so, does anyone have a code sample they could share?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jan 2023 11:13:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/reading-proplist-values-in-a-maapi-script/m-p/4751984#M7600</guid>
      <dc:creator>tcragg1</dc:creator>
      <dc:date>2023-01-10T11:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: Reading proplist values in a MAAPI script</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/reading-proplist-values-in-a-maapi-script/m-p/4752223#M7601</link>
      <description>&lt;P&gt;You mean reading with a script after provisioning?&lt;/P&gt;&lt;P&gt;If you dump the service instance with ncs_load with flags like '-M -U -o' you will see that there is no convenient 'proplist' node.&lt;BR /&gt;If I remember proplist does persist so my guess would be that NSO stores proplist in the private/diff-set gibberish under the instance or somewhere else entirely. First is not useful at all, second would be cool to know if true.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jan 2023 15:23:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/reading-proplist-values-in-a-maapi-script/m-p/4752223#M7601</guid>
      <dc:creator>u.avsec</dc:creator>
      <dc:date>2023-01-10T15:23:22Z</dc:date>
    </item>
    <item>
      <title>Re: Reading proplist values in a MAAPI script</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/reading-proplist-values-in-a-maapi-script/m-p/4770138#M7664</link>
      <description>&lt;P&gt;Yes, there is a &lt;FONT face="courier new,courier"&gt;private/property-list/property&lt;/FONT&gt; list in each service instance:&lt;/P&gt;
&lt;LI-CODE lang="python"&gt;In [2]: with ncs.maapi.single_read_trans('admin', 'python') as t:
   ...:     s = ncs.maagic.get_node(t, '/foo-service{bar}')
   ...:     for p in s.private.property_list.property:
   ...:         print(p.name, p.value)
   ...:
k1 v1
k2 v2&lt;/LI-CODE&gt;
&lt;DIV&gt;You can also access it in the CLI if you &lt;FONT face="courier new,courier"&gt;unhide fastmap-private&lt;/FONT&gt;.&lt;/DIV&gt;</description>
      <pubDate>Tue, 07 Feb 2023 07:16:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/reading-proplist-values-in-a-maapi-script/m-p/4770138#M7664</guid>
      <dc:creator>markozagozen</dc:creator>
      <dc:date>2023-02-07T07:16:07Z</dc:date>
    </item>
  </channel>
</rss>

