Object Number Series

5 Responses

1. I have the same problem and am wondering how this is possible since I did not use the ACS Tool a lot until this point. The Object Range should be sufficient for a while (the latest ACS Object got the Number 60038), so why is the Tool complaining?

2. If you get the error, then another app has probably used some number within the range. Behind the scenes are no safeguards to prevent another app from “stealing” and unused number.

3. If I understood it correctly, field security is on company level, so every company gets their own app.

   The Object Range is only used at the moment from one ACS Extension for one Company. If I update the Extension there are no problems.

   My problem now starts when I create a security feature for a different company but in the same object range. Then I get an error when publishing.

   Do I have to split my free object range through the amount of companies I have?

4. STOP!

   You should only create features in one company, the extension you create is common to all companies. After you know it’s working in one company, there’s a function to copy the setup to other companies.

   So, build all security features in the same company first.

5. Great misunderstanding on my part then, thanks for the Clarification!