Editing tools are inactive

JohnGoat

Hi,

Editing tools are inactive, how can i edit operation?

CraigGillgrass

Hello, a few things:

Do you have permissions to edit the sde.Default version?
You have 16,000+ features selected. The threshold of bulk editing in the Web Editor is 200 features. Try selecting less features to enable Move, Delete or Copy.

Craig

JohnGoat

Hi @CraigGillgrass

Yes i have a permissions to edits operations. I can edit the same web map in the Map Viewer interface.

CraigGillgrass

thanks @JohnGoat - is the sde.Default version Protected?

JohnGoat

@CraigGillgrass

Thanks

No it is public access

CraigGillgrass

thanks @JohnGoat a couple other questions

Are the editing tools enabled when you have 200 or less features selected?
Is the Create Feature tool, the first one on the Primary Editing toolbar? In your screenshot, you've opened the Utility Network toolbar, so I can't see what the Primary Editing toolbar looks like.
What is your User Type and Role for your named user?

thanks

JohnGoat

1.The situation is the same when I select 1 feature.

2. Yes, As I mentioned in the screenshot, the editing toolbar menu is inactive.

thanks @CraigGillgrass

3. I have a creator user type, Advanced editing add on added to creator.

CraigGillgrass

ok, I think I see the issue @JohnGoat - there's an issue we're working through with respect to licensing of the Web Editor at 11.3. Let's take this over to email so we can sort through this, can you email me at cgillgrass@esri.com

thanks,

lzorloni

Hello Craig,

I think I have the same problem, but I found a not so good "solution"...

When I open the web map in web editor the "Create" and the editing buttons are inactive for me too:

If I go to the Versioning tab, change to another branch version and go back to the Default version, it seems like it fixes.

Maybe a bug?

Thank you,

L

CraigGillgrass

Hello @lzorloni yes, that is a known issue in Web Editor at 11.3 and you're solution is the way to workaround that particular bug. I'll elevate this issue and see if we can get it addressed for the next release.