topic Re: 00396: The dataset version is later than is supported by your server. Minimum version in Electric Questions

00396: The dataset version is later than is supported by your server. Minimum version

RomuldKiobya — Sat, 09 Aug 2025 14:23:51 GMT

Review the attached photo. I wanted to publish feature layers as a web map in ArcGIS Online. I

Re: 00396: The dataset version is later than is supported by your server. Minimum version

JoshuaBixby — Sat, 09 Aug 2025 23:02:41 GMT

What version of ArcGIS Pro are you using?

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RomuldKiobya — Sun, 10 Aug 2025 11:46:06 GMT

ArcGIS pro 3.5

Re: 00396: The dataset version is later than is supported by your server. Minimum version

JoshuaBixby — Sun, 10 Aug 2025 13:43:09 GMT

Have you read 00396: The dataset version is later than is supported by your server. Minimum version: <value> - ArcGIS Pro | Documentation ? That kind of error message is more common when publishing to ArcGIS Enterprise, but one can run into it with ArcGIS Online in specific situations.

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RomuldKiobya — Mon, 11 Aug 2025 06:07:39 GMT

It does not make sense I'm using ArcGIS Online not ArcGIS Enterprise. I don't have controll of servers from clouds. I'm using latest desktop application. It means Esri don't upgrade servers that used in clouds.

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RossStrachan3 — Mon, 11 Aug 2025 07:12:55 GMT

This may be coming from field compatability between your UN based feature layers and what is supported by ArcGIS Online. Take a look here Field Types in ArcGIS Online, Best Practices and Compatibility

Depending on the UN schema version you are using you may find that your feature classes have unsupported (in AGOL) types.

Best

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RomuldKiobya — Mon, 11 Aug 2025 13:02:19 GMT

2022 and 2023 when I used ArcGIS pro 2.9 I published was okey no problem. But when I started to use PRO 3.5 problem is coming.

Re: 00396: The dataset version is later than is supported by your server. Minimum version

JoshuaBixby — Mon, 11 Aug 2025 13:25:57 GMT

Did you publish this exact same dataset to ArcGIS Online using Pro 2.9, or were you speaking in general about pushing to ArcGIS Online from Pro 2.9? If this dataset was copied or created with a newer version of ArcGIS Pro, it might be one of the datasets has an incompatible data type.

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RossStrachan3 — Mon, 11 Aug 2025 14:03:05 GMT

Hello again,

If your UN based feature classes have been upgraded over time with new releases of the UN schema at new versions of ArcGIS Pro this would have modified data types on your feature classes.

You can see the history here Utility network upgrade history—ArcGIS Pro | Documentation

In particular, if you have updated to UN schema 7 it uses a new 64 bit datatype for objectid which I don't believe is fully supported in AGOL at this time.

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RomuldKiobya — Mon, 11 Aug 2025 14:11:43 GMT

It doesnot make sense, All over the world data types are known (interger,text, float/double) and attachment. What is new primary data type ?

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RomuldKiobya — Wed, 13 Aug 2025 07:02:08 GMT

It is not my fault, It is Esri. Not all people can afford Enterprises subscription. We use AGOL to connect with Field Map (enables data collection). After that, I migrate GDB from AGOL to GDB on ArcGIS Pro 3.5 to continue with the processing of UN Validation and other QA & QC issues.

Re: 00396: The dataset version is later than is supported by your server. Minimum version

RossStrachan3 — Wed, 13 Aug 2025 17:02:56 GMT

Hi Romuld,

I don't think anyone is pointing blame here not to you nor to Esri - just trying to work out how to help to solve your interesting problem.

If I understood your workflow:

1. You manage your UN in a FGDB (or mobiled GDB) in single-user mode i.e. no Branch Versioning, no ArcGIS Enterprise.

2. Periodically you publish it to AGOL for use with Field Maps.

3. Periodically you extract and consolodate the Field Maps updates into your local UN using Pro.

You used to use Pro 2.9 now you are using 3.5.

I was suspecting the new 64bit objectid type might be causing your issue but I have just published a webmap to AGOL with an empty UN that has 64bit objectids (using Pro 3.3.5).

If you have made sure everything is compatable perhaps raisng a support case is your best option now.

Best