<?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: Why does Calc stage to write to nested collection field then report as an error in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Why-does-Calc-stage-to-write-to-nested-collection-field-then/m-p/90370#M40595</link>
    <description>Hello Derek,&lt;BR /&gt;&lt;BR /&gt;I've just checked as far back as 6.2.1 and can see this validation error back in that version as well, but I can't say for sure what version it was introduced in.&lt;BR /&gt;&lt;BR /&gt;I believe that the issue causing this validation error was resolved in 6.7 under BG-3570, the release note for which reads:&lt;BR /&gt;&lt;EM&gt;Using a Calculation stage to write a value to a nested collection no longer causes a validation error.&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;I've just tested and can confirm that my process that gives this validation error doesn't generate the same error in Blue Prism 6.7 or later.&lt;BR /&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;Regards,&lt;BR /&gt;Rob&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Robert Nicklin&lt;BR /&gt;Senior Product Owner&lt;BR /&gt;Blue Prism&lt;BR /&gt;Warrington, England&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Thu, 03 Dec 2020 21:10:00 GMT</pubDate>
    <dc:creator>robert.nicklin</dc:creator>
    <dc:date>2020-12-03T21:10:00Z</dc:date>
    <item>
      <title>Why does Calc stage to write to nested collection field then report as an error</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Why-does-Calc-stage-to-write-to-nested-collection-field-then/m-p/90369#M40594</link>
      <description>I can write to nested collection field with a calculation stage, but error checker detects this as an error.&lt;BR /&gt;"Field 1.a does not exist in collection"&lt;BR /&gt;Even if collection (e.g. A) is single row collection with 2 feilds (e.g. A.1 &amp;amp; A.2) with nested single row collection (e.g. A.1.a &amp;amp; A.1.b)&lt;BR /&gt;&lt;BR /&gt;I can use Collection Manipulation - Set Field action (without error) but not a quick and convenient as dragging the field from a collections field into calculation stage.&lt;BR /&gt;&lt;BR /&gt;I am using v6.6&lt;BR /&gt;Is this just an issue in v6.6 ? &lt;BR /&gt;I don't recall this issue in prior versions.</description>
      <pubDate>Thu, 03 Dec 2020 01:12:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Why-does-Calc-stage-to-write-to-nested-collection-field-then/m-p/90369#M40594</guid>
      <dc:creator>DT</dc:creator>
      <dc:date>2020-12-03T01:12:00Z</dc:date>
    </item>
    <item>
      <title>RE: Why does Calc stage to write to nested collection field then report as an error</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Why-does-Calc-stage-to-write-to-nested-collection-field-then/m-p/90370#M40595</link>
      <description>Hello Derek,&lt;BR /&gt;&lt;BR /&gt;I've just checked as far back as 6.2.1 and can see this validation error back in that version as well, but I can't say for sure what version it was introduced in.&lt;BR /&gt;&lt;BR /&gt;I believe that the issue causing this validation error was resolved in 6.7 under BG-3570, the release note for which reads:&lt;BR /&gt;&lt;EM&gt;Using a Calculation stage to write a value to a nested collection no longer causes a validation error.&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;I've just tested and can confirm that my process that gives this validation error doesn't generate the same error in Blue Prism 6.7 or later.&lt;BR /&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;Regards,&lt;BR /&gt;Rob&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Robert Nicklin&lt;BR /&gt;Senior Product Owner&lt;BR /&gt;Blue Prism&lt;BR /&gt;Warrington, England&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Dec 2020 21:10:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Why-does-Calc-stage-to-write-to-nested-collection-field-then/m-p/90370#M40595</guid>
      <dc:creator>robert.nicklin</dc:creator>
      <dc:date>2020-12-03T21:10:00Z</dc:date>
    </item>
    <item>
      <title>RE: Why does Calc stage to write to nested collection field then report as an error</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Why-does-Calc-stage-to-write-to-nested-collection-field-then/m-p/90371#M40596</link>
      <description>Thanks Rob that's good news (when we get to v6.7+)&lt;BR /&gt;Thanks for the confirmation.&lt;BR /&gt;In the meantime I have changed all stages to use collection manipulation to have a clear error log&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Derek&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Dec 2020 21:30:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Why-does-Calc-stage-to-write-to-nested-collection-field-then/m-p/90371#M40596</guid>
      <dc:creator>DT</dc:creator>
      <dc:date>2020-12-03T21:30:00Z</dc:date>
    </item>
  </channel>
</rss>

