We are constantly bumping up against our AO count when deploying to QA. It'd be nice to have better metrics on AO counts when deploying so we can manage this better.

I agree with you PJ, I also faced similar issue while pushing the code from dev to test.

My dev has the unlimited object limit but when it comes to test or prod it's limited. so whenever I push to test, during the last step of deployment it showed me the error saying object limit is full and that doesn't make sense.

Exactly! It would be nice if they could tell us that we'd exceed our limit before going through the entire process. Put a red marker on any applications that are too big to deploy with a note that it will break the limit.

Hi PJ & PP,

If you are near to AO limit then OS warn you at the top of service center with the warning message. You can see Used % in respect to Allocated AO %.

Lifetime is simple, if we show everything then after sometime it become complicated. You can also check AO in service center.

Thanks,

Rajat Agrawal

Rajat, looking at Used % doesn't really help. If I have 10% Unused AOs, does that mean I have enough available to deploy my solution or not? Firstly, there is no easy way to see how many AOs a solution will consume, so you need to manually estimate that. Secondly, surely Lifetime should calculate the number of AOs that will be consumed upfront, and check that there are sufficient available before it starts with the deployment.

We think it would be beneficial to have an application object count on the deployment pages of the application section of Lifetime.

Perhaps having a count of the number of objects you are pushing from Dev to Test and the number of objects already being consumed in Test.  Currently, the lack of this functionality has a negative impact on our development in cases where our order for more objects is working it's way through our procurement and accounting departments, but we cannot deploy any new modules since we can't identify easily how many are needed for a given deployment.