Project Tasks - Is there a way we could have 5000 task lines?
Are there any solutions out there that would allow for upwards of 5000 task lines on a project? We realize there are limitations based on tiers, but we are getting stopped when we upload a certain number of rows to populate a cost budget.
Are we misunderstanding the line upload limitation as an upload is the same as a “commercial transaction”?
Or is there a way to do Parent Projects and Subprojects? Are there any solutions out there that would tackle that?
Would love to hear anyone’s ideas. Thank you!
Page 1 / 1
@acheesman The # of tasks falls under the Maximum Number of Lines Per Transaction.
Thanks Heidi, yes, we ran into that, and wondered if there were other marketplace solutions like having parent projects and multiple linked sub-projects. I saw a customization project a few years ago with that kind of feel, but am having a hard time finding who I saw the demo from. This style might work so they can split these larger projects up into phases and still be able to stay within the maximum number of lines for their license tier. We have tried lots of scenarios of different ways to do it, but the client still wants to see that level of detail. Thanks for responding to my question.
Hi @acheesman ,
This topic has come up recently and I was looking to see if you can provide the example cost budget lines. I’ve had situations where builders want to use task as a unit / lot / phase and related cost budget lines can exponentially grow based off of the related numbers.
Other areas revolved around reporting and billing at the project task level. Consolidated/Rolled-up, individual, multiple customers, etc.
Any examples you have will help as we design options.
Thanks.
Joel
Thanks Joel for checking this out. Here is a screenshot of a project task list they have. This one only has 4 different tasks per unit. But as they track other tasks per unit and have bigger properties they are doing it for, the list will grow.
Thanks so much!
Depending on your tolerance for a workaround, one option would be to introduce a new project attribute called "Parent Project", then reference or join on that attribute for reports and inquiries. Alternatively, your VAR could customize the screen to support this functionality more directly.
Regardless of which approach you choose, it's important to consider the number of reports and inquiries that would need to be updated to support this logic. Depending on your use case and how you plan to work with the 5,000+ task codes, it may be more effective to look at the transaction tier instead and increase the number of lines per transaction.
One thing to keep in mind is the human element. If you rely on an attribute, users will need to enter the parent project code accurately for it to work as intended.
Hope this helps point you in the right direction. Robert
