Most feature classes that I create in ArcPro will be used in map viewer to be used in an instant app, experience builder app and Field Maps.
If ArcPro had a check box where we could select where we plan to use the data, and ArcPro could limit our symbology to what is available in the apps, and the character length to what can sync offline, and any other setting that will need to be reconfigured once the data is published online in order to get it to work properly in the desired application that would be great.
I spend a bunch of time formatting things in ArcPro to lose the symbology etc when I publish, or find that I have to modify the settings all over again once I publish online.
One example is the simplified date without time option that is available in Arc Pro. If it isn't compatible with all applications, once I select the application I plan to use the data in, there should be a warning that tells me I need to use the date with time instead in order to have it work in the application.
Example:
Click the checkbox below to limit the settings of this feature class to be compatible in the following applications:
Map Viewer
Experience Builder
Instant Apps
Field Maps
Thank you for your submission. Regarding symbology, are you aware of the Use symbol types compatible with all clients check box which is available when you configure web feature layers? This setting may help handle symbol rendering in different applications.
@JonahLay I have used it a tiny bit. I'm in that awkward stage right now where all of my apps are still in Map Viewer Classic, Web app builder, and field maps.
I am publishing new layers and am trying to create new apps using the new map viewer and instant apps and field maps, and some experience builder apps. The data still has to work in the old apps too in the meantime. It is getting confusing knowing which settings will be compatible and which settings will work in one app and break in another.
It seems like it would be easiest to see where it will work or won't work when publishing from ArcPro.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.