<?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: What is the best practice for publishing a survey to more than one portal from Connect? in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1413581#M56385</link>
    <description>&lt;P&gt;Thank you everyone for the advice.&amp;nbsp; I am going with two surveys.&amp;nbsp; Making a copy of the dev survey once's it's been fully approved for production.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This also allows a copy of the dev survey to be ready, if any additional survey enhancements are required after deploying to Production.&lt;/P&gt;</description>
    <pubDate>Mon, 22 Apr 2024 16:31:44 GMT</pubDate>
    <dc:creator>RyanBohan</dc:creator>
    <dc:date>2024-04-22T16:31:44Z</dc:date>
    <item>
      <title>What is the best practice for publishing a survey to more than one portal from Connect?</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1408805#M56155</link>
      <description>&lt;P&gt;What is the best practice for publishing a survey to multiple portals from Connect?&lt;/P&gt;&lt;P&gt;We are working on making better use of our QA/DEV portal environments for &lt;STRONG&gt;testing&lt;/STRONG&gt;, and only publishing a Survey to ArcGIS Online or our Enterprise Portal once its ready to go into &lt;STRONG&gt;production&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;I am not sure the best practice for doing this within connect.&amp;nbsp; Would it be better to make the survey and publish to QA/DEV, and make a &lt;STRONG&gt;copy &lt;/STRONG&gt;(save as)&amp;nbsp;of the survey within connect when it's ready to go into production? Or can the &lt;STRONG&gt;publishing location&lt;/STRONG&gt; be easily changed with &lt;STRONG&gt;Manage Portals&lt;/STRONG&gt; in Pro?&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;It seems like there is something in the source files for the survey that tags the survey as already published, even though the publishing location has been changed.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Have &lt;STRONG&gt;two&lt;/STRONG&gt; surveys within connect does seem easier, if there are any future modifications, as they can be applied and published to our test environment first then transferred to the Production survey.&amp;nbsp; With the&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;caveat of getting to make any changes twice.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RyanBohan_0-1712872545796.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/100749i4EF96E0691E4B204/image-size/medium?v=v2&amp;amp;px=400" role="button" title="RyanBohan_0-1712872545796.png" alt="RyanBohan_0-1712872545796.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thank you Esri community!&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2024 22:32:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1408805#M56155</guid>
      <dc:creator>RyanBohan</dc:creator>
      <dc:date>2024-04-12T22:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for publishing a survey to more than one portal from Connect?</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1410407#M56221</link>
      <description>&lt;P&gt;I go with two separate files. One for Production, and one for testing server.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 16:41:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1410407#M56221</guid>
      <dc:creator>abureaux</dc:creator>
      <dc:date>2024-04-16T16:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for publishing a survey to more than one portal from Connect?</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1410520#M56233</link>
      <description>&lt;P&gt;If there is something very specific that needs to be different between your environments, you will need two separate files. However, I usually use only one file.&lt;/P&gt;&lt;P&gt;I always test my survey in a TEST/QA/DEV environment first. Once everything is working correctly, I switch my active connection to the PROD environment and publish my survey.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 18:53:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1410520#M56233</guid>
      <dc:creator>RejeanLabbe</dc:creator>
      <dc:date>2024-04-16T18:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for publishing a survey to more than one portal from Connect?</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1413581#M56385</link>
      <description>&lt;P&gt;Thank you everyone for the advice.&amp;nbsp; I am going with two surveys.&amp;nbsp; Making a copy of the dev survey once's it's been fully approved for production.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This also allows a copy of the dev survey to be ready, if any additional survey enhancements are required after deploying to Production.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 16:31:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/what-is-the-best-practice-for-publishing-a-survey/m-p/1413581#M56385</guid>
      <dc:creator>RyanBohan</dc:creator>
      <dc:date>2024-04-22T16:31:44Z</dc:date>
    </item>
  </channel>
</rss>

