topic Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed. in ArcGIS Indoors Questions

Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

SamuelMonat — Fri, 13 Oct 2023 15:36:11 GMT

Hello,

After doing the tutorial, I'm trying to use the Update Occupant Features tool with a csv file containing only two lines for two occupants on a units feature layer. I checked that both values in the UNIT_ID field are an exact match with the units features as well as for the USE_TYPE, OFFICE_NAME, FACILTY_NAME, LEVEL_NAME, LEVEL_NUMBER and VERTICAL_ORDER fields. Yet, when I run the tool, two lines are added in the occupant features as expected, but nothing shows up on the map and all of the fields are empty. I get this warning: 2 occupant assignment(s) could not be processed.

Is there something that can cause the match between UNIT_ID values to fail?

Thanks!

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

KadeSmith — Fri, 13 Oct 2023 15:43:14 GMT

At first read this sounds like you've done everything correctly, but screenshots of the data used and the geoprocessing field mappings might help a little here.

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

SamuelMonat — Fri, 13 Oct 2023 15:49:29 GMT

Thanks for the response, here is a screenshot of my csv file and the geoprocessing I'm running:

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

KadeSmith — Fri, 13 Oct 2023 16:00:09 GMT

Everything looks good to me. A few things I would look at/try:

Verify that the UNIT_ID in the CSV matches exactly to the UNIT_ID in the Units feature class (I'm guessing you already did this)
Make sure the version you are working in is reconciled against default and that you are viewing the latest version (this has gotten me before where I updated some data and I thought it wasn't working, but I forgot to refresh my version to see the changes.)
I would try running it without the record that contains the accent in the unit id for Jim Baird. It's possible the special character might be an issue (doubtful, but possible).

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

SamuelMonat — Fri, 13 Oct 2023 16:10:47 GMT

Still no luck, it is strange that the record appears in the occupants features, but the matching with UNIT_ID does not seem to work. Do you know if the other fields are used as well in the matching process?

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

KadeSmith — Fri, 13 Oct 2023 16:12:57 GMT

Sorry, I don't know. Are you able to manually assign the occupant to the unit? If so, does everything match up in the occupant table after the assignment to the CSV?

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

SamuelMonat — Fri, 13 Oct 2023 16:51:14 GMT

I have tried to assign manually the UNIT_ID in the attribute table of the occupants features but it doesn't seem to match up on the map or with other fields.

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

KadeSmith — Fri, 13 Oct 2023 16:55:12 GMT

I was asking if you are able to manually assign the occupant to the unit using the Indoors Space Manager app? If you are, do so and then compare the occupant feature class row that is assigned with the CSV.

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

SophieFrank — Sat, 18 Nov 2023 00:37:16 GMT

Hi @SamuelMonat, are you still experiencing issues with this workflow? If so, could you send a screenshot of your Units layer attribute table to take a look at the UNIT_IDs that match the ones in the spreadsheet?

Regarding your question "Do you know if the other fields are used as well in the matching process?" -- No, the tool just looks at the inputs for the following parameters: Unit Identifier (input unit features) and Unit Identifier (input occupants table)

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

MykenzieHirata — Mon, 22 Jan 2024 18:21:37 GMT

Hello,

I am an intern working on indoor mapping for my university. My internship partner and I are having the same issue. However, when we did the ESRI training it was successful and had no problems, but now trying to recreate that training but with our own data we are running into the same issue. We are thinking it is an issue with our unit ids, but not sure how to troubleshoot this further.

Did you ever resolve this issue? If so what steps did you take to resolve it?

Thank you!

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

Zrobinson_SFPUC — Fri, 13 Sep 2024 16:29:29 GMT

Hello, did you ever resolve this issue? Having the same problem here.

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

Zrobinson_SFPUC — Wed, 25 Sep 2024 16:43:47 GMT

I was able to resolve this issue with Esri Support. The problem was that I had "null" values in the Assignment Type field of my Units layer. Once we calculated all of the null values to None values, then the tool worked as expected.

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

JaceBrown — Fri, 27 Dec 2024 16:58:33 GMT

Hi,

I ran into the same issue. To get a successful import, I included only the following fields in my "Input Occupant Table:" Known As, Email, Site ID, Contact Phone, Job Title, Org_Level_1, Org_Level_2, Start Date.

Furthermore, I left the "Unit Identifier (Input Occupant Table)" blank. These changes resulted in a successful import.

I was also attempting to assign the occupants to specific Units and Levels based on their respective IDs located in the Indoors attribute tables. However, those attempts resulted in repeated failures. I believe that functionality may be reserved for Indoor Space Planner in ArcGIS Online.

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

AaronKoelker — Thu, 08 May 2025 22:17:24 GMT

I'm running into a similar issue as well, but none of the suggestions so far have worked for me. The weird part is I have two (supposedly) identical copies of my Indoors Database (fgdb) and feature classes, and it works on one set and not the other.

About half the occupants match and the other half do not. In the text log that the GP tool generates the message for each that doesn't match is: example@email.com could not be assigned to 'xyzxyzxy' because the unit's ASSIGNMENT_TYPE value is not None or Office, or the unit does not exist in the input Units layer.

The matching Unit IDs are there, I can even search them exactly from the input table to the Units table and get a match. There are no leading or trailing space. And the Assignment types are all Office or None, but I even tried setting them all back to None. Truncating the Occupants and trying again also results in the same issue. None of the units have a Null Assingment Type, either.

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

SophieFrank — Thu, 08 May 2025 22:49:18 GMT

Hi Aaron,

When you calculated the Assignment Type field to None, did you use the string "None" or the domain code "none". If the former, could you try calculating the field to "none" to match the domain and see if you still face the same issue?

Re: Update Occupant Features returns warning: Occupant assignment(s) could not be processed.

AaronKoelker — Fri, 09 May 2025 15:45:13 GMT

Hi @SophieFrank

I did use the lower case 'none' domain code when calculating the values, and afterward in the attribute table in showed the domain description 'None', so it seems to have been setting the domain value correctly.

For now, I ended up just copying the working copy of the FGDB I had. Hopefully it was just user error somewhere along the line, but I've run out of ideas and need to move on.

Thanks