Why can't we edit the labels for the default client information yet?

[Joe_Carrick]

FWIW, I have a macro hidden on my Layout Template (page 0) that reads the text file(s) an get's all the info.  It executes when the Layout is opened but it's coded so that it will only execute once.

 

It stores that data in $Global variables that can be used in anyplace in both plan and layout.  The text files are unique to each project.

 

Basically, it just expands the functionality missing in the Designer/Client Info tool.  It would be a lot better if this sort of functionality was built-in to Chief.

[Alaskan_Son]

I have my own systems for creating custom project information "fields".  Information is all entered in a single location in the plan or layout file, custom fields can be created on the fly, and I don't use globals anymore.  That being said, I'm a little curious why more people don't just use plain old non-evaluated text macros.  Its a very very easy way to create custom fields that can be exported/imported as well.

[SHCanada2]

On 7/9/2025 at 11:35 AM, Alaskan_Son said:

That being said, I'm a little curious why more people don't just use plain old non-evaluated text macros.  Its a very very easy way to create custom fields that can be exported/imported as well.

That's what I do for detail parameters, but after I saw Rene's point and click system for details, I did realize his is a lot nicer (no typing, and not looking at a long list of macros in the TMM), which is why I thought if we could actually write to the text based macros, with a macro, then it is one and done.

 

But I did forget about the import function. For those that store data outside in files, good question, why not just import directly into the text macro...formatting maybe?

 

 

[Alaskan_Son]

25 minutes ago, SHCanada2 said:

....which is why I thought if we could actually write to the text based macros, with a macro, then it is one and done.

 

I agree.  This functionality would be awesome.