topic Re: Pro 3.5.5 broke all our Arcade $datastore calls giving Object not found $datastore in ArcGIS Pro Questions

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

DougBrowning — Wed, 11 Feb 2026 16:26:35 GMT

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

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

Robert_LeClair — Wed, 11 Feb 2026 16:32:57 GMT

One way to test if 3.5.5 "broke" the $datastore item is to uninstall 3.5.5 and revert back to 3.5.4 and then retest.

For Windows 10, you can uninstall the ArcGIS Pro 3.5.5 service pack by going to Control Panel->Uninstall a program->(top left) View installed updates->then click the ArcGIS Pro Patch 1 (3.5.5) and uninstall.

For Windows 11, MS made it a bit more difficult, see image below:

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

DougBrowning — Wed, 11 Feb 2026 16:53:10 GMT

Our computers are all managed we cannot do any of that. Plus these all get called sever side in geoprocessing tools so changing one computer will not help.

Why would it be saying datastore is not valid?

Again all our production geoprocessing tools are now broke. This is a very major issue for us.

thanks

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

Robert_LeClair — Wed, 11 Feb 2026 17:01:51 GMT

Okay - digging deeper, I believe this is BUG-000182720 - "Arcade expressions using FeatureSetByName($datastore, ...) fail to validate in layout dynamic texts in ArcGIS Pro, returning the error “Object not found $datastore.” It's currently under review. The issue is not reproducible in ArcGIS Pro 3.4 and earlier but 3.5 and above.

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

DougBrowning — Wed, 11 Feb 2026 17:06:40 GMT

Well that is exactly what we are using. Umm ok wow this is bad. Any know workaround at all? Like I said it took down most of our tools for 6,000 users. So yeah its bad.

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

Robert_LeClair — Wed, 11 Feb 2026 17:13:29 GMT

In reviewing the Esri Support case logged 2/11/26, I do not see a workaround currently in the case documentation. I understand that this is a high-impact bug to your organization and I wish I had an answer for you. Although not a solution, I would contact Esri Support Services and have your organization's customer number associated with this BUG certainly.

Again, not a great solution I know, especially with such a large organization, but uninstalling 3.5.x and reinstalling 3.4.x would allow those tools to work again.

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

CraigWilliams — Wed, 18 Feb 2026 19:09:51 GMT

The Arcade Layout profile (https://developers.arcgis.com/arcade/profiles/layout/) does not support the $datastore profile variable or the Data Access function bundle. Validation was updated at the 3.5 release to more strictly enforce profiles and this case that previously had been undocumented and unsupported behavior stopped working. Furthermore, in ArcGIS Pro 3.6 the code editor now includes profile-specific code hints to indicate when variables outside the scope of the profile are in use. We understand from your viewpoint that this is a regression in functionality, but execution of such scripts was accidental and as mentioned above unsupported and undocumented. Including support for feature set functions and profile variables such as $datastore may be considered for a future enhancement, but feature set functions are generally not included in drawing profiles due to performance impact. An alternative approach would be to perform the necessary computation in a calculation attribute rule and consume the calculated field.

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

AlfredBaldenweck — Wed, 18 Feb 2026 21:01:12 GMT

Interesting. Is the layout profile considered "drawing"? As far as I know, Arcade is really only available as dynamic text or table attributes in Layout.

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

DougBrowning — Wed, 18 Feb 2026 21:35:40 GMT

These are for layouts that make dynamic text on the fly based on input from a custom geoprocessing tool. So attribute rules would not work for that since the polygon is on the fly that is being summarized.

So your idea will not work. We need some way to grab data from other layers here please!

Note this has been working perfectly for years and years so makes no sense to remove it now. Esp with no alternative. This is a HUGE deal for us as all of our Production tools are still broken. We took one machine and downgraded to 3.3 to get us by but we just have to have this going forward. We use it to look across 15 123 forms to create QA reports. It has been a huge hit and we even won an Esri award for it.

I am super confused why time is being spent removing features here. Please help @CraigWilliams .

Thank you

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

DougBrowning — Wed, 18 Feb 2026 21:36:42 GMT

@Robert_LeClair We did get one computer back to 3.3 and it all works again now. We really, really need this fixed going forward. Thank you

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

DougBrowning — Thu, 19 Feb 2026 14:33:22 GMT

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

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

LoganShank — Thu, 19 Feb 2026 16:32:15 GMT

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:

Official confirmation whether this change was intentional for 3.5.5 and, if so, the rationale,
A timeline for restoring functionality (via $datastore, $map, or an alternate), and
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

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

AlfredBaldenweck — Thu, 19 Feb 2026 16:55:50 GMT

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

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

Robert_LeClair — Fri, 20 Feb 2026 21:42:07 GMT

@KoryKramer - FYI

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

BrianFahringer1 — Fri, 06 Mar 2026 11:36:44 GMT

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.