Would be nice to have custom properties that are specific to the MLESO types. Currently, I’m initiating these custom properties at the Items/Products Lists, some Assemblies, some Project.
I keep seeing a place where I’m hiding all by default but know that I have a group of 10-13 Items/Products or specific resource type assemblies targeted for a MLESO type (more specifically, Labor & Material) that I wouldn't leave hidden for targeting MLESO item/assembly type
Would be a great helper if we were able to give a description (alt text) helper to our custom settings so we don’t have to jam up the variable name with extra symbols/characters

Also, as noted above it would be nice to have MLESO assembly types as well. I’m guessing the workaround, I’ll be testing out this week, is to create a template MLESO Item/Product as well as assemblies and just use those as the templates? Curious to hear what others are doing with assemblies and custom properties.
Also, still lobbying for tabbed navigation bar on the project sheet where global variables can be set that influence a lot of MLESO types, or could be assemblies. If I understand correctly, when these variables are set at the project level all properties set at as Custom Setting that are set to “inherit” will pick up the global variables set at the project level…
I tested this out a little and it didn't go as planned, at least for assemblies. About to test a Labor type.
Am I not making the right connection/understanding? As in, I expected these fields to already be populated from the information I set at the project level.
Do I have to set these variables at the start for items to pick-up, not at mid-stream?


Hi, you need to add this Template's type to the custom properties, and set its value to Inherit for the default of this type on the custom properties dialog.
Thanks @Stephen for the response. I may be getting my nomenclature incorrect.
I thought I had set the assemblies type to inherit the variable/property?

Hi Chaz, I tested this now with a new project and a new takeoff and a new item, and they all worked as expected. You should note that if you update your custom properties AFTER creating the takeoffs or items, they will not auto populate with the inherit setting, as this is limited to the create operation to set the inherit.
Thanks for the follow-up and checking this out @Stephen
Can't check it out just yet, but looking forward to seeing what's possible