How to select all line features that intersect with another point layer?

[MargoHuang]

Hi all,

I am on Enterprise 11.3 and trying to configure my Experience Builder app so I can select records from one line layer that intersects with another point layer. I have tried Select Widget and Query Widget, but they are not returning the same amount of records as the result of Select By Location in Pro with the exact same layers. 

With Query Widget, there is no way to pass all records from a layer, so I manually selected all records from the point layer. But it is not giving me the expected result. I guess maybe it is not designed to process the entire layer.

With Select Widget, I can pass all records from the point layer. But 0 records are returned when I run it. I am pulling my hair off and can't figure out how to get this simple function to work.

Below is the result of running select widget. The Roots Defects layer is a point layer and has 309 features in it. The Wastewater Inspection Run Layer is the line layer. I am trying to return inspection runs that have the roots defects points on top of them.

When I run Select By Location in Pro using the exact same layers, I got 114 records returned. This Pro project is what I used to published the layers.

Has anyone encountered this before? Any insights are appreciated.

Thanks!

Margo

[DavidPike]

It may be the maxRecordCount of your feature layer if you're able to adjust it in Server or Portal.

[MargoHuang]

Hey David,

Thanks for the help! It looked like that could be it. I tried upping the max Record Count so the number is bigger than my line feature records, but it still returned 0 records 😕

Margo

[Ke_Xu]

Hi @MargoHuang,

I couldn't reproduce this issue on Enterprise 11.3. Could you share the webmap for me?

Could you try try the Default view and check if there is any result returned?

Thanks,

Ke

[MargoHuang]

Hey Ke,

Thanks for looking into this. Our portal is behind our firewall unfortunately. I do have it set to Default, so that's not the issue. The line feature has over 100,000 records. Do you think that could be an issue?

I tried @DavidPike's suggestion and upped the Maximum Number of Records Returned by Server to 200,000, but it still returned 0 results. 

Here is the other thing I tried - I published these 2 layers to AGO. It returned no results when I disabled buffer. However, when I set the buffer to 1 feet. It returns the exact same amount of records as in ArcPro. 

I tried to test 1 feet buffer in Portal 11.3 with the Max Record set to 200,000 but had to kill it after it spined for over 10 minutes. Applying 1 feet butter with the Max Record set to 2,000 returned 4 records.

Any ideas on what might be the issue?

Thanks a lot!

Margo