Welcome, Guest. Please Login
Tinderbox
  News:
IMPORTANT MESSAGE! This forum has now been replaced by a new forum at http://forum.eastgate.com and no further posting or member registration is allowed. The forum is still accessible via read-only access for reference purposes. If you wish to discuss content here, please use the new forum. N.B. - posting in the new forum requires a fresh registration in the new forum (sorry - member data can't be ported).
  HomeHelpSearchLogin  
 
Pages: 1
Send Topic Print
Possible bug re Renaming User Attribute (Read 809 times)
Ralph Alvy
Full Member
*
Offline



Posts: 85
Santa Monica
Possible bug re Renaming User Attribute
Jan 14th, 2015, 11:03am
 
I had a boolean User Attribute called UserChangelog. Various items in my outline had that Attribute checked for future reference. I decided to shorten that Attribute's name to Changelog. Renaming it resulted in all the items that had UserChangelog checked not having Changelog checked. So the Attribute Name was not cascaded or inherited. It seems as though renaming it resulted in it being replaced, not renamed.
Back to top
 
 
  IP Logged
Mark Anderson
YaBB Administrator
*
Offline

User - not staff!

Posts: 5689
Southsea, UK
Re: Possible bug re Renaming User Attribute
Reply #1 - Jan 14th, 2015, 11:36am
 
This is a similar issue to your question re deleting  attributes vs key attributes (KA). KA are stored in the system attribute $KeyAttributes. It is a list [sic] of attribute names. Thus if a note’s KA are $FullName, $StartDate, $EndDate and $UserChangelog, the stored list value is "FullName;StartDate;EndDate;UserChangelog".

Now if as explained elsewhere if you delete an attribute or alter it's name, only the attribute is affected. TB doesn't - and never has - go through and find any/all references to the attribute name in KA, agent queries, rules, export templates, etc., etc., and change/delete them. That is left for the user; in anything but a trivially simple document 'just' auto-updating such changes would be more complicated than you might assume.

Tip: if you use Key Attributes a lot, use prototypes. Then the rule, KA, etc. can be edited once and instantly corrected in many notes.

But, you say, I've got lots of notes with existing KA. I applied a prototype and they aren't inheriting the prototype's KA as they're locally set.

Extra Tip: rest your KA using a stamp.  Use this stamp code:

$KeyAttributes=;

Now select all the notes to reset and apply the stamp. They will now inherit the prototype or app default KA value.  The same process applies for any attribute, just use the '=;' method:

$AnyAttributeName=;

You can reset several at once:

$AnyAttributeName=; $ThisAttribute=; $ThatAttribute=;

…and so on.
Back to top
 
 

--
Mark Anderson
TB user and Wiki Gardener
aTbRef v6
(TB consulting - email me)
WWW shoantel   IP Logged
Pages: 1
Send Topic Print