Pro 3.5.5 broke all our Arcade $datastore calls giving Object not found $datastore

[DougBrowning]

I think this was when we went to Pro 3.5.5 all of a sudden all our Arcade using $datastore in layouts in dynamic text broke.  We have tons of these.

We are getting

Object not found $datastore

on code that has worked for over a year at least.

Simple code here that calls to SDE.  Tried with and without SDE prefix etc.  Again this all worked for years.

FeatureSetByName($datastore, "I_Indicators", ['*'], false)

We had it nested under Filter but pulled it out for testing.  I do not see how datastore can not be valid?

Not finding anything at all out there on this.  Tried $map and does not work which I get.  But why is datastore suddenly gone?

Appreciated the help all our production stuff is now down so we are desperate.

thanks

[DougBrowning]

Is there a reason $map does also not work?  That would work for us but it is not working also.

[LoganShank]

Removing the $datastore Arcade profile from ArcGIS Pro Layouts is a significant regression for users who rely on dynamic text expressions to drive quality control and consolidated reporting from multiple related tables. Our team has used $datastore successfully for years to generate one‑page Data Summary PDFs (via map series) that combine values across many layers and related tables and apply custom QA flags. When $datastore stopped resolving in 3.5.5 (“Object not found $datastore”), these summaries and the QC flow they enable were immediately impacted.

Why this matters

• Dynamic text beyond Min/Max/Avg/Count: Layouts are most powerful when Arcade lets us query and compare values across related tables and parent layers. That’s how we surface missing, unusual, or inconsistent data in a way crews can act on without opening attribute tables or bouncing between maps.
• Production automation: We run nightly jobs to generate page‑per‑site summaries from multiple services and repeat tables; $datastore is the only practical way to stitch those relationships directly inside the layout so analysts see the whole picture in one page.
• Performance: Even with >40 expressions per page, layout performance has been acceptable and stable relative to other Pro tasks. Removing $datastore isn’t justified on performance grounds from our experience.

Request

If $datastore must be removed from the Layout profile, please add an equivalent—for example, make $map available in Layout Arcade so expressions can reference layers in the project’s map(s). Today, Layout dynamic text doesn’t recognize $map, and documentation indicates $map availability varies by profile (e.g., popups vs. field calculations). Bringing either $datastore back or enabling $map in the Layout profile would preserve long‑standing workflows without forcing users to re‑platform.

What we’ve tried

• Reverting to a prior Pro build restores behavior, but that’s a temporary workaround and not feasible long‑term for enterprise environments.
• Re‑implementing in Reports/Dashboards or pre‑aggregating outside the layout undermines the single‑page QC workflow and removes the ability to craft targeted flags from related tables at render‑time.
• Attribute rules are not an acceptable solution and do not solve any of the problems listed above.

Additionally, please provide:

1. Official confirmation whether this change was intentional for 3.5.5 and, if so, the rationale,
2. A timeline for restoring functionality (via $datastore, $map, or an alternate), and
3. A migration path for users with existing Layout Arcade expressions.

We’re happy to share sanitized .pagx and a list of expressions illustrating the QC logic. Thank you for considering a path that keeps Layouts a first‑class home for serious data QA.

@CraigWilliams @Robert_LeClair 

[Robert_LeClair]

@KoryKramer - FYI

[AlfredBaldenweck]

Made an Idea for this: https://community.esri.com/t5/arcgis-pro-ideas/arcade-add-datastore-and-map-to-the-layout-profile/id...

[BrianFahringer1]

I just opened a map that relies on $datastore to summarize data in the current map extent and also summarize project totals, and it no longer appears to be working. This is disappointing, as I spent many hours building these maps around that functionality. I hope this change can be reverted or addressed soon.