Copying Items Between Databases Doesn't Bring Custom Attributes Properly

[TimP]

Perhaps I'm expecting something extraordinary. When I copy template items with custom attributes and forms based on those attributes, the custom attributes don't follow properly and the form row that contained those attributes are empty.

The help says that all of this shouldn't be a problem. Is there an approach to inducing the correct behaviour?

[quant]

works as expected here, can't think of the reason why that wouldn't work ...

[kinook]

That works ok in our tests (tested by copying some books from the Books.urd sample to a new database).

[TimP]

Sigh.

I've never actually seen the feature function as expected. I just now did it again, and it fails exactly as I describe.

I drag a new template I've created, based on the document template with new attributes and a custom form that includes those attributes. The template item in the target database is missing some (not all) of the new attributes and the form is different because of the missing attributes.

So, I've attached a tiny version of the source database that I've been using. If any of you can drag the template item "Research Document", in tact, with all attributes and the form, into a new empty database, I'll have to be surprised.

[quant]

confirmed, the attributes are there, but the form is incorrect.

[TimP]

for sure all attributes? "Cited" and "significance" and "research reference" appear to be there, but "Value", "Analysed" and "Publication" attributes don't appear in the target.

[quant]

ok, I found the most probable reason for your problem.

The form contains attributes that "Research Reference" does not, hence the problem ...

[TimP]

Nice call! And thanks for taking the trouble to understand this problem. UltraRecall and its excellent user community strike again!

So, forms do not carry attributes to items they're assigned to. I can certainly see both sides of the discussion that might ensue from this. However, I would definitely side with those who think a form carried around by a template should carry its attributes into derived items instead of their just sort of floating in the form.

I hope Kinook will figure out how to deal with this. The help page titled "Form" under "Getting Started > Basic Concepts > Attribute > Attribute Type >" states that a form is an alternate method "for viewing and editing the item's attributes." I've had a good look around, and nowhere is there a mention of attributes having to be assigned to an item before a form can be used in such a manner. As much as there's a warning that attributes could be lost when changing the template of an item, I would think that a similar caution about the comings and goings of forms would be equally helpful.

[quant]

Originally posted by TimP
However, I would definitely side with those who think a form carried around by a template should carry its attributes into derived items instead of their just sort of floating in the form.
form in only a frontend, so I believe Kinook will fix this oversight so that set of form "attributes" is neccessary subset of the set of template's attributes (or alternativelly automatically add the new ones to the set of template's attributes).

[kinook]

Yes, at this time, you do need to add all form attributes to the template in order for inter-db copy to include all form attributes.

[goggin]

Is this why when I copy the Journal Year template from the provided sample file and paste it into my practice db, it doesn't work as advertised?

That is, highlighting a given month and hitting insert is supposed to produce a Journal child item with today's date as the title, but instead I get a text child item.

I get item attributes (i'm pretty sure, anyway), but don't get the role the "form" plays in the discussions above...that's why I'm not sure I've understood this thread correctly. And I definitely don't know what is meant by "copying form attributes to a template."

Thx in advance for the help...
--
dg

[ashwken]

Originally posted by goggin
Is this why when I copy the Journal Year template from the provided sample file and paste it into my practice db, it doesn't work as advertised?

That is, highlighting a given month and hitting insert is supposed to produce a Journal child item with today's date as the title, but instead I get a text child item.

I get item attributes (i'm pretty sure, anyway), but don't get the role the "form" plays in the discussions above...that's why I'm not sure I've understood this thread correctly. And I definitely don't know what is meant by "copying form attributes to a template."

Thx in advance for the help...
--
dg
Apparently the Templates are losing the Default Child Attribute value when copied to the new database.

At first I copied the Year Template to a New db, which produced it self, plus its child Templates (Month, Journal Entry), plus it created a second Month Template. The creation of the individual Month and Journal Entry Templates is to be expected since they reside as children of the Year Template, but the creation of the second Month Template is strange. Shift-Delete all copied Templates.

Next, I copied just the Journal Entry Template, then the Month Template, then the Year Template. In this case the Month Template did not duplicate, but the Default Child Template value is lost.

Next, I copied some Templates from one of my db with the same results, the Default Child Template value is lost.

Other Attributes values are retained (Icon, Form, Title Expression).

Running UR v.3.5e.

[kinook]

This is fixed in the latest download (UltraRecall.exe version 4.1.2.4 in Help | About | Install Info). Thanks.

[goggin]

Thank you! Once again, your responsiveness is amazing...and appreciated.
--
dg