Feature Requests

Is there a way to lock a component ID after it has been generated? If not, this would be a very valuable feature. On most jobs, devices have a very different Component ID requirement. It would be nice to be able to protect items' ID from being inadvertently being updated when changing others.

I think the new submittals feature is pretty great so I wanted to provide some feedback on how this tool, or more specifically the framework of this tool, could be utilized to improve SI's feature set. There are a ton of docs that could be included in a submittals package that aren't BOM related. Shop Drawings, network coordination sheets, change narratives, etc. The list goes on and on. It would be nice if we could include additional categories from the project files list to be included in the submittals report. Separately, it would be rad if this tool could be used as a document assembly tool. Specifically, a way to take several files and combine them all together into a master document. Like a proposal PDF paired with a sheets describing a custom service plan and a third warranty statement. Etc.

While I'm sure we are all VERY appreciative of the new dark mode in v21, it would be rad if the UI wasn't completely void of all color. While my eyes are no longer on fire, thank you BTW, the monochomatic UI elements no longer have the ability for easy visual identifaction of icons, check marks, etc. Can we pepper some color back in?

Appreciate the client .exe that was sent. but we have a few issues. As a minimum we need to see that fix applied as a min as a direct fix thru the app as a patch. SI in-app updates are whitelisted for users to apply, but not other .exe files. 1st. Our PC's are locked down, requiring our IT management company to get involved to schedule user availability and implementation on every PC for an additional fee. Currently we have appx 28 users that use D-tools at one point or another. 2nd. This individual client setting approach does not ensure our (FBA) Followed-By-All methods. Preferred: Would be the implementation of the fix as admin only server-based system wide enforced setting. Ensuring all users adhere to our (FBA) Followed-By-All procedures. Of course, an admin sub setting of allowing the clients to choose H:M:S vs Dec. could also be an option... You know for all those loose and free organizations out there. Thinking forward... Should the feature request for catalog updates/request directly from within the clients be implemented. The server enforced requirements would ensure the catalog info remains consistent and FBA.

We need the ability to group resources into groups, and then display the groups in the calendar (not each resource).

Need the ability to allow for the Accessory of Accessory to show when linked to items. This needs to be a priority as it is possible in other software systems.

Would be nice to be able to add a file shortcut to the files list on a DT project that links to a network shared resource. Like a shortcut to Excel document that others populate but don't necessarily have access to DT.

We are needing additional options to filter in the Time Sheet Explorer, the most important being filtering by Project Manager. This way a PM can go in and filter by their name and see all the time posted to any of their projects. We've been trying some work arounds and it's all turning out to be very time consuming. Second, we are needing the ability to save custom layouts in the Time Sheet Explorer. We are doing lots of resizing and moving of columns each time we approve time.

Would be a great feature to have for looped wires. The headend can say AV Rack or Lighting Control Panel, or Network Rack. Then, on drawing, we can have same coponent ID cable, which can be duplicated by using Paste Aleternate Shapes. Then to which ever devices we connect those alternate shape copies of the wires, the comp IDs and device name and locations can be shown as list of connected devices on loop. This can work for speakers on long loop, like 70V line, or even lighting circuits. Maybe we might need a new kind of Wire called bulk loop, where we might not track to and from devices, but list of devices. And the bulk and finish wires will have usual two device record for To and From, and headend.