850 Bug - Importing of Variables

[Duncan Rounding]

It appears that there is a bug in V850 that has occurred since 804.
An hierarchical import of variables does not change the values of the variables.

I have tested a variable created and set to Section. On importing, the variable does not update as it used to in 804. Any variable assigned is reset to Use Parent().

Is this a known issue?
When will it be addressed as it is very important to be able to do this?

[Duncan Rounding]

Any comment on this issue Chris please?

[cdicken]

Hi Duncan

How are you importing the variable? Is it via a 'partial site design'?

I have always found (even in 8.0.4) that when you include a variable or a layout selector in a partial site design that it will overwrite the instace of the variable that you have in the library and reset all settings for that variable back to whatever you have set for the 'Initial Value'.

If you give an example of what you are looking to do, perhaps I can make some suggestions.

[Duncan Rounding]

No not a parial design just an ordinary hierarchical import such as:

Header:Section,"Section name","MyVariable"

Section,"SectionName","test"
End,Section

The Variable has been defined with Place of Setting: Section, Type: Text.
It worked fine in 804 but leaves the Value as Use Parent() in 850.
there are no errors on importing.

[cdicken]

Hi Duncan - can you give me some example data to look through? Maybe just a couple of example sections and products. I can test this for you.

My email address is cdicken /at/ actinic /dot/ co /dot/ uk.

[Duncan Rounding]

Email sent - Thanks Chris.

[cdicken]

Hi Duncan

As confirmed via email, there does seem to be a problem importing values for user-definable variables into 8.5.0 via a hierarchical import file. I'm waiting for the developers to confirm this and come up with a workaround for you.

[bentleybloke]

I'm having the same problem now. Do you have any news, please?

Thanks!
Jonathan

[cdicken]

Yep - As a workaround, we have created a 'Catalog.exe' file which just has this one issue fixed in it. If you contact Actinic Support via phone or email) they can send you the file.

This fix will be included in the next maintenance patch of Actinic.

[DaveSMR]

I appreciate this is a long time dead issue but having read it over I think I'm having a similar problem in 9.0.5.

Any user-defined variables I have that have been intentionally set to disallow use-parent (thus are blank), or use a boolean true/false value are being reset to Use Parent(), if the "section path" is used in a hierarchical import. Other user-defined variables (that have been defined with a string) are not being set to Use Parent().

Is it possible this is related in anyway? I'm surprised it hasn't come up before.