| Altus Docs

Software boundaries and limits

Task management

Detail	Supported Limit
Number of projects	5000
Number of tasks/project	300

Detail	Supported Limit
Baselines per Project	20

Resourcing

Detail	Limit
Dataverse quota consumed per resource year.	170kb / Resource / Capacity Year
Default Capacity Horizon	4 years / resource, 1 in arrears and 3 ahead.
Maximum Capacity Horizon	11 years / resource, typically 1 in arrears and 10 ahead.
Maximum Supported Resources with calendars	2000 Resources with 4 years of capacity planning (1 behind 3 ahead)
Single view size for Display/Edit/Save in resource grids: Resource Plan Resource Demand Bookable Resource Allocation Availability Heatmap	45 resource years, e.g.: 540 resources rows for 1 month 180 resources rows for 3 months 90 resources rows for 6 months NOTE: When grid is grouping by project, it is the number of expanded resource rows that are counted for this limit. Use view filters to maintain performance levels.

Timesheeting

Detail	Limit
Expected Dataverse quota consumed per timesheet with 100 rows fully populated	375 kb / Timesheet
Supported number of rows per Timesheet	100 rows

Scheduled processes

Detail	Limit
Maximum results to be returned from FetchXML query in a Scheduled Process	500
Maximum runtime for a Workflow Extension called from a Dynamics Workflow	120 seconds (this is a platform limit)
Maximum number of days Process Logs will be kept	30 days

Name Fields

Where possible, the primary Name fields in Altus have been set to 500 characters to allow maximum flexibility.

There are some tables/entities where the Name field has been limited differently - usually because there are limitations elsewhere where error or issues would result if the character limit was increased. It is recommended not to modify these character limits in Altus.

These include the following:

Table/Entity Name	Name Field	Character Limit	Note
Bookable Resource	Name	358	Bookable Resource Names should be limited to 255 characters. The additional character limit is present so that in the case of externally synced Resources they can be safely appended with the name of the External System.
Portfolio	Name	255	Portfolios can be configured to be owned by a Microsoft 365 Group. Length maximum needs to match that of a Group name.
Program	Name	255	Programs can be configured to be owned by a Microsoft 365 Group. Length maximum needs to match that of a Group name.
Project	Name	255	Projects can be configured to be owned by a Microsoft 365 Group. Length maximum needs to match that of a Group name.
Proposal	Name	255	Proposals can be promoted/approved to become Projects and the name length needs to match that of a Project.
Task	Name	256	Task names need to be managable and flow on to other areas of Altus (e.g. Timesheets) where they need to display succinctly.

In addition, the sync tables used for External Systems have been configured such that the incoming Project Names, Task Names and Resource Names align with the limits defined above.

Note: Tables internal to Altus (where their entry is not exposed to users) will vary in Name length.

Some additional Microsoft related field lengths which may be useful as reference: