0 votes

I'm troubleshooting a weird issue with the "Create User" form and the business rules behind it. The error that's being returned is that the "Company" property doesn't meet the following contstraint: must be one of: "CompanyA" or "CompanyB". The weirdness is that the error only occurs for a single Office value in a list of multiple values.

Some additional details:

  • The Create User from sets "CompanyA" as the default value when the form is opened.

  • In addition to the "Company" User Pattern, we're also setting the "Office" information which updates the account's address information.

  • For the "Office" selection, the business rule iterates through an "If - ElseIf" for multiple office values. For example:

      If the operation succeeded AND
          the "Office" property equals "Location1" then
          modify the user: [set the L2 address information]
          Else if the "Office" property equals "Location2" then
          modify the user: [set the L2 address information]
          Else if the "Office" property equals "Location3" then
          modify the user: [set the L3 address information]

    And so on, through many other office locations.

Other office locations in this "If - ElseIf" logic complete successfully, with no error and the address is populated. For example, let's say that "Location5" is the location that throws the error. If I create an account with "Location4" or "Location6", the account is created and the address information is populated.

In addition, when I hover over/view the specific "Create" event in the logs I can clearly see that the "Company" value is being set with the "CompanyA" value.

I'm really having a hard time understanding why this one value would fail. Thoughts?

Thank you, -Todd

by (70 points)

Hello Todd,

For troubleshooting purposes, please, provide us with a screenshot of the execution log for user creation that has the issue. For details on how to view the log, see https://www.adaxes.com/help/ViewOperationsPerformedViaAdaxes. Please, make sure that the screenshot includes all the records. Also, please, provide us with a screenshot of the full business rule you referenced.

You can post the screenshots here or send to us at support@adaxes.com.


This issue has been resolved.

Turns out that when setting the address information for this specific location, the "Company" attribute was used when trying to set the value for the "Country". The value, in this case, being "US".

Since "Company" has a contstraint that is something other than "US", the account update failed and threw the error.

Looked at the error more times than I care to admit and failed to see that mistake. Many thanks to Adaxes Support for the extra set of eyes.

Please log in or register to answer this question.

Related questions

0 votes
1 answer

Dear support, Property patterns for date are currently barely usable. You can define that the value must be: - One of the following values only - Must not contains the ... but it would look cleaner if the property pattern could handle that natively. Cheers !

asked Mar 8, 2019 by Pierre (750 points)
0 votes
1 answer

Hello, We encoutered an issue with Adaxes in default configuration. We are mainly using Adaxes for its REST API, to automate identity lifecycle with our HRIS. We tried to update ... got enforced even on an API REST attribute change? If so how to disable it?

asked Aug 18, 2022 by ygini (240 points)
0 votes
1 answer

Is there an order of precendence for Property Patterns? If I set a property pattern at a level lower than another property pattern is set what happens? Will one work and the other won't?

asked Aug 18, 2020 by ComputerHabit (790 points)
0 votes
1 answer

How can I check or run reports on an entire Property Pattern to ensure integrity? I know I can run a check on an individual property, but this is really inefficient since I have already defined a Property Pattern for a specific object to abide by.

asked Jul 16, 2014 by chazlander (120 points)
0 votes
1 answer

Hello, I am trying to create a custom command that handles the process of converting a user account for a temp to a FTE. This needs to: 1. move the user to a new OU. 2. change ... to "xxx" OU Set 2: Always --Modify the user: set employee type to...... etc.

asked Jul 26, 2013 by DFassett (710 points)
3,430 questions
3,127 answers
546,252 users