<?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: Update Metadata Based on Data in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875026#M20719</link>
    <description>&lt;P&gt;Unfortenately there is no functionality OOTB to enforce metadata attributes to an existing table.&lt;/P&gt;
&lt;P&gt;So this has to be managed more or less manually. I can imagine that there are some utility scripts out there, if you are lucky someone might share it.&lt;/P&gt;
&lt;P&gt;The manual way is to use PROC DATASETS (for formats and labels). If your table has a Table Loader step, you can copy paste part of the code from there.&lt;/P&gt;
&lt;P&gt;If the table structure has changed in other ways (data types/lengths, dropped/added/renamed columns) the table has to be recreated. In this case I would defintely go for a manually and controlled process - change/release management.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Question is how big the problem is.&lt;/P&gt;
&lt;P&gt;If user access the libnames assigned by the server, most applications use metadata attributes in UI at least.&lt;/P&gt;</description>
    <pubDate>Wed, 10 May 2023 16:45:58 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2023-05-10T16:45:58Z</dc:date>
    <item>
      <title>Update Metadata Based on Data</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875016#M20718</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;
&lt;P&gt;I have a situation where the "physical table metadata" (output of proc contents) are poorer than the "metadata server metadata" (metadata visible through e.g. DI Studio) so we would like to update the "physical metadata" based on the "server metadata" - the opposite of (as I understand) what PROC METALIB does. Any ideas &lt;span class="lia-unicode-emoji" title=":thinking_face:"&gt;🤔&lt;/span&gt;?&lt;/P&gt;
&lt;P&gt;Many grateful TIA&lt;/P&gt;
&lt;P&gt;Anne.&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2023 16:30:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875016#M20718</guid>
      <dc:creator>Anne_A</dc:creator>
      <dc:date>2023-05-10T16:30:00Z</dc:date>
    </item>
    <item>
      <title>Re: Update Metadata Based on Data</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875026#M20719</link>
      <description>&lt;P&gt;Unfortenately there is no functionality OOTB to enforce metadata attributes to an existing table.&lt;/P&gt;
&lt;P&gt;So this has to be managed more or less manually. I can imagine that there are some utility scripts out there, if you are lucky someone might share it.&lt;/P&gt;
&lt;P&gt;The manual way is to use PROC DATASETS (for formats and labels). If your table has a Table Loader step, you can copy paste part of the code from there.&lt;/P&gt;
&lt;P&gt;If the table structure has changed in other ways (data types/lengths, dropped/added/renamed columns) the table has to be recreated. In this case I would defintely go for a manually and controlled process - change/release management.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Question is how big the problem is.&lt;/P&gt;
&lt;P&gt;If user access the libnames assigned by the server, most applications use metadata attributes in UI at least.&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2023 16:45:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875026#M20719</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2023-05-10T16:45:58Z</dc:date>
    </item>
    <item>
      <title>Re: Update Metadata Based on Data</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875070#M20720</link>
      <description>ENORMOUS Thanks &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13674"&gt;@LinusH&lt;/a&gt;!</description>
      <pubDate>Wed, 10 May 2023 20:05:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875070#M20720</guid>
      <dc:creator>Anne_A</dc:creator>
      <dc:date>2023-05-10T20:05:26Z</dc:date>
    </item>
    <item>
      <title>Re: Update Metadata Based on Data</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875362#M20729</link>
      <description>&lt;P&gt;You could use this macro to create an empty dataset using the metadata definition:&amp;nbsp;&amp;nbsp;&lt;A href="https://core.sasjs.io/mm__createdataset_8sas.html" target="_blank"&gt;https://core.sasjs.io/mm__createdataset_8sas.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then find some way to append the data into it.&amp;nbsp; Perhaps by using this macro to export:&amp;nbsp;&lt;A href="https://core.sasjs.io/mp__ds2csv_8sas.html" target="_blank"&gt;https://core.sasjs.io/mp__ds2csv_8sas.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could then use a tool such as &lt;A href="https://datacontroller.io" target="_blank"&gt;https://datacontroller.io&lt;/A&gt;&amp;nbsp;to do the import (drag &amp;amp; drop the CSV back into the new table definition).&amp;nbsp; Feel free to get in touch if you need assistance, we built the tool.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 May 2023 22:10:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Update-Metadata-Based-on-Data/m-p/875362#M20729</guid>
      <dc:creator>AllanBowe</dc:creator>
      <dc:date>2023-05-11T22:10:35Z</dc:date>
    </item>
  </channel>
</rss>

