nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Map "unable to open. Width must be 0 or grater"

RafaeldePedro

Hi, can anyone help with this issue. I have got a couple of maps that will not open on Field Maps (or on Collector). They are similar in setup to all the other maps which do open and work fine. When trying to open the map, I get the message: "Unable to open width must be 0 or greater.

Screenshot with message also attached.

I can't see any posts with this issue but I'm hoping someone will know the reason.

Thank you

Screenshot_20220215-125658_Field Maps.jpg

meetsandboundshelp.PNG

Vind meer berichten getagd met

Accepted answers

cgillgrass

The issue seems to be with the second last layer in your map; TEST_RevA_Phase1_LAYERS - Phase 1 habitats (Areas). When I remove that layer, I can open the map in Field Maps.

I'm not sure what's wrong with that layer - but wanted to post this in case you could see what the issue is.

ZacharySutherby

Hello @RafaeldePedro,

Please feel free to add ZSutherby_Survey123 to the group and I'll be happy to assist with taking a look into the behavior. To confirm are you using Survey123 version 3.14, if so are the questions that you are seeing not receive their URL values relevant based on other question(s) that are also receiving URL values? If that's the case we do have a known issue with 3.14 were relevant questions aren't correctly receiving URL values, please see this Esri Community post. We do have a fix planned in our March update which is planned to be released this afternoon.

All comments

RafaeldePedro

Someone from ESRI staff? Any help please?

RafaeldePedro

Second attempt at getting an expert from ESRI to look into this topic please?

I had several layers in the map, and I deleted all the features previously created directly on AGOL, in case some geometry issue was causing the problem, but it made no difference.

This is pretty bad as the message gives me no clue of what is wrong, and I can't find any similar posts on ESRI Community so please any help at all would be very appreciated.

shan_sarkar

Hi @RafaeldePedro ,

1. Is your app is up to date to the latest ?

2. Can you confirm if there were any changes in to your AGOL role?

3. What type of device are you using? (Android or Apple)

4. What is your AGOL subscription status? (Active or suspended)

cgillgrass

Hi @RafaeldePedro the easiest way for us to troubleshoot this is to get access to the web map. Can you invite the "craig_sp" user to the group the map is in so I can try it out to see what the issue is?

Based on the error message, my guess is this points to something schema related; a field or property of the web map, but we'll know more when we take a look.

thanks,

RafaeldePedro

Hi Shan, thank you for your reply. To answer your questions:

1. Field Maps app version is 22.0.1

2. No changes to my AGOL role.

3. Android (Samsung)

4. Active

Basically, we have over 100 webmaps in our organisation site, which are all available to any user with the right permissions. However, this maps I've done show this new problem I haven't seen before. They have been done (by me) by publishing from ArcMap (Share as a service) where the layers were feature classes of a geodatabase I had just modified (I modified some fields, domains and subtypes). It all publishes without problem, and I can open the map on Collector for Windows on my laptop. It's just when using Collector or Field Maps on a smartphone or tablet that the error message appears.

Thanks for looking into this.

RafaeldePedro

Hi Craig,

I have created a group in our organisation and called it "Troubleshooting". I found you and sent you an invite so hopefully you received it. I have also shared the webmap and all related items with the newly created group.

Please let me know if you can access it fine.

Thanks for your help.

Rafa

cgillgrass

The issue seems to be with the second last layer in your map; TEST_RevA_Phase1_LAYERS - Phase 1 habitats (Areas). When I remove that layer, I can open the map in Field Maps.

I'm not sure what's wrong with that layer - but wanted to post this in case you could see what the issue is.

RafaeldePedro

Ah! Ok that's weird. I will investigate and re-do from scratch again and see what happens. But thanks for finding out that really helps me go in the right direction!

cgillgrass

Hi @RafaeldePedro this might be a new issue - can you keep the layers as they are? I'll see if we can debug it to get this addressed.

I saved a copy of the map for our use - but need that particular layer to remain.

thanks,

RafaeldePedro

Hi @CraigGillgrass - I think what went wrong is that the two bottom layers I had given them the same name in ArcMap when I published the service (Phase 1 Habitats (Areas)). I did rename them already in AGOL but I don't think this has fixed it. I think I have to re-name them in ArcMap before publishing, which I am about to test. I have changed the names back in AGOL to what they were when they raised the error and it all should look the same in the webmap as when I came here with the question, so please feel free to access it and continue to investigate.

Thanks again for your help,

Rafa

RafaeldePedro

Hi again @CraigGillgrass.

I have managed to fixed the issue - it was not caused by the two layers being shared with the same name. The layer that was causing the problem was setup in a GDB as a Feature Class where the field SecondaryHab is an integer with subtypes. I'm not sure what went wrong, but I have created the Feature Class again from blank and recreated the fields, subtypes, etc. and it is working now in AGOL/Field Maps.

However, I have found a new issue, unrelated to the original, but since you have access to the webmap and feature layers can you please have a look? All layers in the webmap have pop-ups with a hyperlink to Survey123. I have tested it and I see that the parameters I'm passing from Field Maps to Survey123 are not shown in the form (PrimaryHab, SecondaryHab, FeatureID and Notes). This link has worked before and now suddenly it isn't (This doesn't affect the link in the hedgerow layer popup). The Webmap, Feature Layers and Survey123 form should all be accessible - could you please have a look, or tag another member of staff who takes on this sort of query, so I can grant them access?

Thank you.

Rafa

cgillgrass

Hello @RafaeldePedro I'm not able to open the map in the Troubleshooting group; not sure if there's another map I should be using?

RafaeldePedro

@CraigGillgrass I don't know why that's happened. I haven't moved the map anywhere. I include a screenshot of the contents in the Troubleshooting group. The map TEST_Phase1_v6_RevB is there and should be accessible. It's the one with the original error which is now fixed (in a different map, not in the Troubleshooting group). But both the new map and the original Rev B map with the faulty layer contain the popup and hyperlink that opens a Survey123 form with missing information.

cgillgrass

I'm unable to open the map in Field Maps; I see the invalid argument error on iOS. I'll need access to the map in Field Maps in order to test this out.

RafaeldePedro

@CraigGillgrass I'm very sorry - I haven't done any changes -at least intentionally- to any of the elements in the Troubleshooting group that should affect access to it. What would cause this invalid argument error?

I will try to create a copy/new map with the same Survey123 hyperlink issue.

Thank you

RafaeldePedro

@CraigGillgrass hi again - still, not sure why you wouldn't be able to access it the map on Field Maps. Nothing had changed as far as I know. However, I have shared new content in the Troubleshooting group you're member off. A new set of layers and three webmaps (all the same really, just slight revisions/variations), all of which present the same issue of the faulty behaviour when invoking Survey123 via hyperlink.

Can you please check if you have access to any of these maps on Field Maps, in order to investigate the problem with the missing values on Survey123?

Thanks again,

Rafa

cgillgrass

Hi @RafaeldePedro it looks like you have a few extra spaces " " in the url you're using to open Survey123. I removed them and setup a new url in for the ag1 polygon and saved a copy of the map as Troubleshooting_Phase1_B-Copy.

It appears to be working for me; but I don't know what should be passed. I do see that in the Survey, the Type of form is pre-populated and Habitat description is selected.

Craig

RafaeldePedro

@CraigGillgrass thank you for all your help so far. I'm sorry that this is dragging - however it is still not working and I don't know what to do to fix it. I could not see the spaces in the url you are referring to, and I couldn't see the Phase1_B-copy map either.

The hyperlink does work, to an extent. It does open a new Survey123 form, and in the first page, it is like you say pre-populated with the option "Habitat Description". The problem comes in the next page, where there should be four fields pre populated, but instead, they all come empty.

'PrimaryHabitat' or Primary Habitat,
'SecondaryHabitat' or Specific Habitat,
'FeatureID' or Habitat ID Number and
'Collector Notes' or ArcGIS Collector Habitat Notes.

These are the names and labels, respectively, on the Survey123 xlsx form.

See below for the popup content and the hyperlinks that I assign to each layer in the map - this is what I have used before, but now it just doesn't work anymore.

FIELD MAPS/COLLECTOR POP UPS

Phase 1 AREAS, Phase 1 LINES and Phase 1 POINTS
{PrimaryHab}
{SecondaryHab}
{FeatureID}
go to Survey123

Water LINES
{FeatureType}
{FeatureID}
go to Survey123

Hedgerow LINES
Hedgerow {FeatureID}
go to Survey123

SURVEY123 HYPERLINK

Phase 1 POINTS, LINES and AREAS (Phase 1 Survey123 Form)
arcgis-survey123://?itemID=INSERT_SURVEY_ID&field:Type_of_form=Habitat_description&field:FeatureID={FeatureID}&field:PrimaryHabitat={PrimaryHab}&field:SecondaryHabitat={SecondaryHab}&field:Collector_notes={Notes}

Water LINES (Phase 1 Survey123 Form)
arcgis-survey123://?itemID=INSERT_SURVEY_ID&field:Type_of_form=Habitat_description&field:FeatureID={FeatureID}&field:PrimaryHabitat=Aquatic&field:SecondaryHabitat=None&field:Collector_notes={Notes}

Hedgerow LINES (Hedgerow Survey123 Form)
arcgis-survey123://?itemID=INSERT_SURVEY_ID&field:Type_of_form=Habitat_description&field:Hedgerow_No={FeatureID}

Once again, thank you for your help. If there is anyone else in ESRI that might be interested in looking at this please let me know so I can add them to our Troubleshooting group. Equally, if this should be now part of a different post, please also let me know and I will create a dedicated post for this issue.

Thank you,

Rafa

cgillgrass

@RafaeldePedro this sounds like it's best solved by someone on the Survey123 team whose familiar with their url scheme; I think that might be where the problem lies. I'm wondering if @JamesTedrick or @ZacharySutherby can take a look. If this ends up being a Field Maps issue, they can reach out to me to re-engage.

RafaeldePedro

Thank you @CraigGillgrass . I have sent an invite to @JamesTedrick. However, weirdly I could not find @ZacharySutherby among the users to invite to the group.

RafaeldePedro

@JamesTedrick hi, sorry you've been thrown into this thread - hopefully you can help me. As you'll see in the thread, the issue is with the Survey123 form opened via hyperlink in the map, not passing the values to the fields as specified in the hyperlink text.

I have added you to the group Troubleshooting in my organisation, where all layers and Survey123 form should be accessible. After more investigating, I think there is something in the XLS form of Survey123 (TEST Phase1 Template v6, or 157410_Phase1_S123) that is causing the problem, but I don't know what. I created a copy of the same form (Phase1 Template v6.2_Test1) and removed all questions except for the 5 questions with values passed on from the map via link. When invoking this very short form, the hyperlink worked, but when using the original, complete form, containing many more questions which are not part of the hyperlink text, that is when it fails.

Sorry for the complexity of the problem, and my explaining probably didn't help. If you could have a look, explore the contents of the maps and forms shared with the group, and let me know if anything looks odd to you, I would be very grateful.

If there's anyway I can make this easier for you to look into, please let me know.

Thank you,

Rafa

RafaeldePedro

Hi just a follow up comment to check if @ZacharySutherby or @JamesTedrick have had the chance to take a look at this problem and if there's anything you guys could do to help it would be much appreciated!

Thank you

ZacharySutherby

Hello @RafaeldePedro,

RafaeldePedro

Hi @ZacharySutherby, thank you for replying. I have sent you (ZSutherby_123) an invite to our group please let me know if you haven't received it.

I am using version 3.13.234 on Survey123 Connect. and version 3.14.237 of Survey123. And yes, I think that is correct - the first value we pass in the url is a string 'Habitat description'. All other following questions are relevant, subject to the first question having the value 'Habitat description'.

Perhaps it was a coincidence, but this behaviour started happening only after I made some major updates to the xls form. I ran a test where I stripped all other questions from the xls form, and left ONLY the questions with values passed from Field Maps in the url - and then it worked.

It's great that you have now access to our AGOL group and I will take a good look at the post you shared with me and try a solution for me in there.

Thank you,

Rafa

RafaeldePedro

@ZacharySutherby After testing, I can confirm it is the relevant status of some questions that have their values passed on from Field Maps via url.

I have changed the design of the xls form and removed the first question (which the following fields were subject to) and it works fine. I appreciate that seems to be an bug with the version 3.14 and it should work fine after the fix is released, but I have found this way to work around it by simplifying the form and this solution will work for me.

Thank you for your help!

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.