<?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 Migrating DI Studio to Viya Platform in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Migrating-DI-Studio-to-Viya-Platform/m-p/963449#M29817</link>
    <description>&lt;P&gt;Migrating from DI Studio to SAS Studio Flows in Viya: Challenges and Solutions&lt;/P&gt;&lt;P&gt;Is anyone experiencing difficulties with exporting and importing DI Studio jobs into SAS Studio flows during Viya migration? Our team is encountering specific challenges with mappings and input files. We're seeking recommendations for a more streamlined methodology to effectively migrate DI Studio content to Viya.&lt;/P&gt;&lt;P&gt;Some specific pain points we're facing:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Preserving complex mappings between DI Studio and Studio Flows&lt;/LI&gt;&lt;LI&gt;Managing input file references during the migration process&lt;/LI&gt;&lt;LI&gt;Maintaining job dependencies and relationships&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Has anyone developed best practices or discovered efficient approaches for this migration scenario?&lt;/P&gt;</description>
    <pubDate>Fri, 04 Apr 2025 15:18:24 GMT</pubDate>
    <dc:creator>HaroonHamid_NBS</dc:creator>
    <dc:date>2025-04-04T15:18:24Z</dc:date>
    <item>
      <title>Migrating DI Studio to Viya Platform</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Migrating-DI-Studio-to-Viya-Platform/m-p/963449#M29817</link>
      <description>&lt;P&gt;Migrating from DI Studio to SAS Studio Flows in Viya: Challenges and Solutions&lt;/P&gt;&lt;P&gt;Is anyone experiencing difficulties with exporting and importing DI Studio jobs into SAS Studio flows during Viya migration? Our team is encountering specific challenges with mappings and input files. We're seeking recommendations for a more streamlined methodology to effectively migrate DI Studio content to Viya.&lt;/P&gt;&lt;P&gt;Some specific pain points we're facing:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Preserving complex mappings between DI Studio and Studio Flows&lt;/LI&gt;&lt;LI&gt;Managing input file references during the migration process&lt;/LI&gt;&lt;LI&gt;Maintaining job dependencies and relationships&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Has anyone developed best practices or discovered efficient approaches for this migration scenario?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 15:18:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Migrating-DI-Studio-to-Viya-Platform/m-p/963449#M29817</guid>
      <dc:creator>HaroonHamid_NBS</dc:creator>
      <dc:date>2025-04-04T15:18:24Z</dc:date>
    </item>
  </channel>
</rss>

