Hierarchical import of custom variables always defaults to Use Parent

[DaveSMR]

Hi,

I am using a hierarchical import file, this import contains some custom variables.

The variables have been set up within the desktop edition and have had "Allow <Use Parent> as an option" unchecked.

Some lines for these variables are blank, and upon import the variables have been set to "Use Parent".

Does anyone know why this behaves in this manner, or how to stop it?

Thanks

[Krithika]

Hi David

I will check this for you and let you know.

Regards

[Krithika]

Hello David

This issue is fixed in v11. If upgrading is not an option, then a workaround is possible using a SQL query to remove the invalid values. Please let me know if you have Access, if yes which version and if you would like to try this workaround.

I would also suggest considering upgrading to v11, latest being SellerDeck 11.0.3 which not only contains lot of bug fixes but also new features as mentioned in the Release notes here.

Regards

[DaveSMR]

I have an old version of access (2002 I think). The work around would be great to have.

[Krithika]

Hi Dave

Before running this query, it is strongly recommended to have a backup of the site database.

1. With Actinic v9 closed, open the relevant site folder and find ActinicCatalog.mdb

2. Open the database in Access. If my memory serves right, in Access 2000 series, there should be list-box on the left which allows you to select the objects, from this you need to select Queries and select New from the toolbar above.

3. Select Design view. A small box will appear labelled Show Table. Close this and you should see an icon just below the File menu which looks like the one in the attached image.
Selecting this will open up the Query window. Assuming the window is blank, enter the following query :

SELECT UserDefinedProperties.nUseParentSetting
FROM UserDefinedProperties
WHERE (((UserDefinedProperties.nUseParentSetting)=1));

If this shows a lot of records then run

DELETE UserDefinedProperties.nUseParentSetting
FROM UserDefinedProperties
WHERE (((UserDefinedProperties.nUseParentSetting)=1));

Note : these are 2 separate queries and you will need only one. The first one selects and displays the relevant results in a new table while the 2nd one deletes them.

Once done close the window and save when prompted to. The new query will now appear on the left hand sidebar under Queries. Double click to run it which should remove the invalid values from the database. Hope this helps.
As mentioned above, please remember to back up the database before attempting this workaround.

Hope this helps.

Regards

[DaveSMR]

Thanks Krithika, you pointed me in the right direction with this.

I couldn't use your work around because some of my custom variables make use of the Use Parent function. However, it did force me to look at the tables, where I noticed that the sValue for the "illegally" use parented variables was still present.

I wrote up a select query to link to Variable IDs from within the "Variables" table to the UserDefinedProperties table, and stipulated criteria on each table.

1) Return those variables that do not allow use parent as an option from within the "Variables" table.
2) Return variables that have the value of "1" from the UserDefinedProperties.

This provided me with an exclusive list of variables that had shouldn't have use parent but did. This was then cross referenced by an update query where I simply replaced the "1" value with "0" on the linked (by the UserDefinedProperties nID) values.

As the original data still existed it reverted to previous data and solved all my problems!

[Krithika]

Hello Dave

Thanks for the update. I am glad to know the issue is resolved for you now

Regards