Latest Contributions by AaronKoelker

Have you tried running the Upgrade Indoors Database GP tool recently? I've found that often when I start getting errors like this with Indoors data, running this tool resolves the issue. Especially if I was mucking around with schema, domains, or copying layers in and out.

Thanks @RyanUthoff , that's a good catch. I was starting to wonder if it might be something like that—no specific property but determined by the presence or absence of something else. I'll keep poking around with that topFilter / groupByFields parameter.

@RyanUthoff Thanks for the link Ryan, that is one of the examples I'd looked at but I don't believe it answers my question. I believe the type of join (left, right, inner, full) is separate from the join relationship or cardinality (one to one (1:1) versus one to many (1:M)), though I could be mistaken. When you go to create one of these manually in the builder, those are two separate questions/settings. In the documentation, the only values listed for the "type" property are LEFT, RIGHT, INNER, FULL I expect that it treats it as a 1:1 join by default, but unsure how to tell it I want a 1:M.

Hello. I'm attempting to create a Joined View via the ArcGIS API for Python and ArcGIS REST API. I've seen examples that say to first use create_service() to create an empty feature service (with is_view=true) and then use add_to_definition() to add layers and set up the join via "relatedTables". Within the relatedTables is a "type" property to set the join type (LEFT, RIGHT, INNER, FULL), but I haven't found anything on how to set the join operation, aka join relationship (one to one versus one to many). If I go to create a Joined View manually in ArcGIS Online there is an option for it, but I'm unsure how to set this via the API. I've also been unable to figure out how/where to check for this property on existing views that have been created manually (was hoping I could find the property that the API wants from there). There doesn't seem to be anything related to that in the service JSON, though.

@MollyE Ah okay, thanks, that makes sense. I didn't know about that move option in the Space Planner, that's handy. We are using joined views as well for dashboard purposes and have run into some of the same hurdles with schema locks you are. It's manageable, but a lot to keep track of.

@TerezaČernohousová I believe a point only appears when an Occupant is assigned to a Unit, not a Workspace Area. For Workspace areas it just adds a value to the Area ID field in the Occupants feature, in order to relate it to the Areas table.

@MollyE Can you elaborate on the solution, please? I haven't found any settings related to labels in the Space Planner app

I've run into a potentially undocumented limitation with Joined Views and Experience Builder, and am wondering if anyone has run into this before or could replicate/enlighten. As a simplified example—say I have an ExB app with just a Filter widget and a Table widget. The Table widget has two Sheets in it, and both sheets point to different Joined Views which share a common join layer (an ArcGIS Online hosted feature layer (Layer A)) but use different target layers in their joins (two other ArcGIS Online hosted feature layers (Layer B and Layer C)). So one Joined View is Layer A + Layer B and the other is Layer A + Layer C. Layer B and Layer C both share a field that contains common data, let's say colors, as an example. The Color field in both Layer B and Layer C are string fields and do not use Domains, however the Values inside the field do match across both layers. So there is a "Red" in both fields of both layers, a "Green", etc. etc. The only difference between the fields is the name (example: one is "Color" and another is "Colour"). I set up my Filter widget to have a Group Filter set up to "Ask for Values" (Unique), using the Color/Colour fields from my Joined Views. When I go to test, I get a dropdown for Colors as expected and select my choice. In the Table widget, however, only one of the sheets gets filtered. Whichever Joined View in the Group SQL Expression that was used as the "Main field" gets filtered in the table, while the other does not. If I switch the "Main field" in the expression to use the other Joined View, then the other sheet gets filtered in the table, and not the first. Unlike single data filters (non-Group Filters), I can't actually see what the underlying SQL looks like, so I'm unsure if the cause is just that the underlying field name is different across both views. I've never run into that issue using two hosted feature layers, rather than Joined Views. That seems to be the whole point of the Group SQL Expression builder, letting you map values to the filter across different fields. I suspect it's a limitation of using Joined Views, but haven't seen that documented anywhere and I'm hoping that someone can confirm.

Cool feature. Are there any size limits to the Frames length and/or resulting video file sizes to be aware of?

Love this addition, small change but big impact on the feel!

I'm seeing this in ExB as well (ArcGIS Online, not Enterprise)—specifically using a "filter" widget that asks the user to choose values from a dropdown list. The options show the codes rather than the labels. The datasource for the filter is coming via a web map. I have noticed that if I add the hosted feature layer as a datasource directly, rather than going through a web map, then the labels are displayed as desired. This isn't a good work around, however, if you need the filter to interact with a map widget. I also noticed that the issue only happens on a specific field within my source layer. If I build the filter on other fields that have domains (regardless of whether the datasource comes through a web map or goes to the hosted feature layer directly) they show the labels instead of the codes, as desired. To me this seems to indicate there may be an issue or setting set in the web map causing this—but I've been unable to find what. Very weird.

@KyleKeath Standard vs Advanced shouldn't make a difference in enabling floor aware data, so far as I know. Here is the license config info. (You do need Network and 3D Analyst if you're doing Indoor routing stuff). Not sure where exactly in the process you are running into an issue, but you configure the floor aware data within the web map properties. Your services need to be floor-aware too. In ArcGIS Online if you go to your content and look at the hosted feature layer item with all your indoors data, it will specifically say if it is an Indoors Hosted Feature layer instead of just a normal hosted feature layer. To get it to do that, you need to configure a floor-aware map in ArcGIS Pro and publish it as a service. To configure a map in Pro to be floor aware, you need to go into the map properties, find the 'Indoor Layers' section and choose your Site, Facilities, and Levels layers. Then publish the whole map as one hosted feature service with all your indoors layers together.

@ABraun The gif in that linked thread is still accurate, but you're next step would be to put your 3 layers into a group. You can create a group by clicking the ... button to the right of any of those layers and choosing "Group" at the bottom of the menu that appears. Expand the new "Group" layer that was created in the Layers panel and you'll see your one layer inside of it. Next, drag the other two layers inside of the group as well (using the six dot handle to the left of the layer name, or you can click the ... button to the right of the layer name again and choose the "Move" option). Sometimes the Move option is easier, as getting the layer to go inside of the group instead of below it via drag can be finicky. You'll know the layer is inside the group if it is indented below the Group Layer row. Once they are all in a group, click on the Group Layer row and go to the Properties tab on the far right of the screen. Scroll down to the visibility section and toggle on the "Exclusive visibility" option. The layers in your group will now have radio button toggles.

@ABraun I thought you were looking at doing this in the basic Map Viewer. It still works there, I just tested it myself. Unsure what happens if you then put it into another app though, like Experience Builder.

@TerezaČernohousová wrote: How does the Indoor Viewer identify me in the list of employees? Is it based on my name - Know As field? @TerezaČernohousová I believe it's based on the Occupants' layer "Email" field, and the app looks to match with the email associated with the user's ArcGIS Online account, which can be found on the account's Profile page.

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by AaronKoelker

Re: Import CAD to Indoors Dataset Errors

Re: How to set join operation (1:1 vs 1:M) when creating a Joined View

Re: How to set join operation (1:1 vs 1:M) when creating a Joined View

How to set join operation (1:1 vs 1:M) when creating a Joined View

Re: Overlapping Occupant labels in Space Planner

Re: No Hotels Available to Book in Indoor Viewer

Re: Overlapping Occupant labels in Space Planner

Filter widget limitations with Joined Views

Re: Create video and PDF files from StoryMaps frames

Re: Small change to standard themes (Obsidian, Ridgeline, Tidal)

Re: Experience Builder - Edit Widget/Tables Domains showing/not showing what determines?

Re: Arc Indoor- Standard and Advanced license

Re: One Layer, several (mutually exclusive symbologies) in a WebMap

Re: One Layer, several (mutually exclusive symbologies) in a WebMap

Re: No Hotels Available to Book in Indoor Viewer

Re: Small change to standard themes (Obsidian, Rid...

Re: Updating config.json results in text widget re...

Append tool "Update (Upsert) Options" being ignore...

Re: Should Append tool perform Update and Add at t...

Re: One Layer, several (mutually exclusive symbolo...