Number formatting does not carryover from Pro to AGOL

926
3
Jump to solution
03-21-2019 09:44 AM
by Anonymous User
Not applicable

Not sure if this is a bug or functionality but when I set up my number formatting in fields view in Pro and then publish to AGOL that formatting does not carryover. I end up having to go back through configure attributes and manually change the formatting for everything. Not only is the table wrong but pop-ups are also reset. Like I said, maybe it's a bug.

Another thing that does not carryover are suffixes. Why have it in Pro but not have the ability to publish to AGOL and have those carryover? Seems pointless especially if I have to make arcade expressions to mimic what I have in Pro.

One last thing that I found interesting is when I publish to AGOL it puts thousands separators in everything. Even if I did not designate thousands separators in Pro. I'm running Pro 2.3.1 by the way.

PRO

AGOL

POP-UP

1 Solution

Accepted Solutions
DanPatterson_Retired
MVP Emeritus

That leaves

ArcGIS Ideas

first to see if it has been posted as an issue, or for you to put forward the idea with your use case.

View solution in original post

3 Replies
DanPatterson_Retired
MVP Emeritus

The amendments/additions to tabular data in Pro are 'fluff' and are just additions to make the underlying data look better.  I am not surprised that you see differences in appearance, however, if the values differ (beyond decimal separators and decimal places), I would be concerned

0 Kudos
by Anonymous User
Not applicable

I understand is just an aesthetic thing but when I'm preparing to present these maps to the public there is a demand for things to appear a certain way. I guess my problem is however I set it in Pro should carryover to AGOL. I should not have to do this twice. In the example I provided there are 55 total attribute fields that need to be changed. I prefer to do most of my work in Pro before publishing and not have to split my tasks up.

DanPatterson_Retired
MVP Emeritus

That leaves

ArcGIS Ideas

first to see if it has been posted as an issue, or for you to put forward the idea with your use case.