<?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 Shared Features and Choice Filters in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/shared-features-and-choice-filters/m-p/1089722#M36560</link>
    <description>&lt;P&gt;I'm hoping this makes sense and if it doesn't, please ask for clarification.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have been puzzling out the issue of shared features and how to represent them on multiple survey for years.&amp;nbsp; Each year our pipelines are inspected by their named line segment.&amp;nbsp; On some occasions, the beginning of pipelineA is the end of pipelineB.&amp;nbsp; Where those two lines meet, there is a valve, let's call it valveAB.&amp;nbsp; When the templates are run, valveAB needs to be on both pipelineA and pipelineB's form.&amp;nbsp; However, it only needs to be inspected once.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do not think that connect has the ability to pull valve info from one survey into another so I've given up on that idea.&amp;nbsp; However,&amp;nbsp;I've been trying to avoid making two list items for the same valve.&amp;nbsp; (Valve AB is still Valve AB whether it's with pipeline A or pipeline B.)&lt;/P&gt;&lt;P&gt;Inspiration finally struck when I realized I could use a choice filter in combination with "or" to make the valve show up on pipeline A, B or C's picklist.&lt;/P&gt;&lt;P&gt;L1_filter = ${clsegname} or L2_filter = ${clsegname} or L3_Filter = ${clsegname}&lt;/P&gt;&lt;P&gt;(cl stands for centerline, aka pipeline)&lt;/P&gt;&lt;P&gt;I've attached two surveys.&amp;nbsp; The one that says "working" is the one I wrote from scratch to test the idea.&amp;nbsp; The one that says "testing" contains copied and pasted code from my actual survey and it does NOT work.&amp;nbsp; Does anyone see what the issue is here?&amp;nbsp; I've tried adding in all the bells and whistles like groups, repeats, etc, into the working copy and it still works.&amp;nbsp; But I can't for the life of me get the testing one to work.&amp;nbsp; It has to be something ridiculously simple but I've been playing with it for two days.&amp;nbsp; Whatever it is, I'm just not seeing it.&lt;/P&gt;&lt;P&gt;Anyone?&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Aug 2021 19:02:45 GMT</pubDate>
    <dc:creator>AllisonHollier</dc:creator>
    <dc:date>2021-08-17T19:02:45Z</dc:date>
    <item>
      <title>Shared Features and Choice Filters</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/shared-features-and-choice-filters/m-p/1089722#M36560</link>
      <description>&lt;P&gt;I'm hoping this makes sense and if it doesn't, please ask for clarification.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have been puzzling out the issue of shared features and how to represent them on multiple survey for years.&amp;nbsp; Each year our pipelines are inspected by their named line segment.&amp;nbsp; On some occasions, the beginning of pipelineA is the end of pipelineB.&amp;nbsp; Where those two lines meet, there is a valve, let's call it valveAB.&amp;nbsp; When the templates are run, valveAB needs to be on both pipelineA and pipelineB's form.&amp;nbsp; However, it only needs to be inspected once.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do not think that connect has the ability to pull valve info from one survey into another so I've given up on that idea.&amp;nbsp; However,&amp;nbsp;I've been trying to avoid making two list items for the same valve.&amp;nbsp; (Valve AB is still Valve AB whether it's with pipeline A or pipeline B.)&lt;/P&gt;&lt;P&gt;Inspiration finally struck when I realized I could use a choice filter in combination with "or" to make the valve show up on pipeline A, B or C's picklist.&lt;/P&gt;&lt;P&gt;L1_filter = ${clsegname} or L2_filter = ${clsegname} or L3_Filter = ${clsegname}&lt;/P&gt;&lt;P&gt;(cl stands for centerline, aka pipeline)&lt;/P&gt;&lt;P&gt;I've attached two surveys.&amp;nbsp; The one that says "working" is the one I wrote from scratch to test the idea.&amp;nbsp; The one that says "testing" contains copied and pasted code from my actual survey and it does NOT work.&amp;nbsp; Does anyone see what the issue is here?&amp;nbsp; I've tried adding in all the bells and whistles like groups, repeats, etc, into the working copy and it still works.&amp;nbsp; But I can't for the life of me get the testing one to work.&amp;nbsp; It has to be something ridiculously simple but I've been playing with it for two days.&amp;nbsp; Whatever it is, I'm just not seeing it.&lt;/P&gt;&lt;P&gt;Anyone?&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Aug 2021 19:02:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/shared-features-and-choice-filters/m-p/1089722#M36560</guid>
      <dc:creator>AllisonHollier</dc:creator>
      <dc:date>2021-08-17T19:02:45Z</dc:date>
    </item>
    <item>
      <title>Re: Shared Features and Choice Filters</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/shared-features-and-choice-filters/m-p/1102215#M37554</link>
      <description>&lt;P&gt;Hi Allison,&lt;BR /&gt;&lt;BR /&gt;You may have already found a solution for this since it's been a while since you posted this, but if you change all the blank choices in the L2_filter list to something like "none" or "NA," then your testing__valve inspection XLS should start working.&lt;BR /&gt;&lt;BR /&gt;-Barbara&lt;/P&gt;</description>
      <pubDate>Mon, 27 Sep 2021 17:30:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/shared-features-and-choice-filters/m-p/1102215#M37554</guid>
      <dc:creator>BarbaraWebster1</dc:creator>
      <dc:date>2021-09-27T17:30:27Z</dc:date>
    </item>
  </channel>
</rss>

