Importing Element Documentation

[ATU]

 I exported the .csv file and changed several hundred Vmemory locations and want to import the new documentation. However, the current documentation still exists in the program and the "delete existing" option is not deleting all of the current documentation when I import the changed .csv file because it is finding duplicate nicknames on memory locations that are not listed in the new .csv file.  I would have thought that when you choose this option, it would have cleaned out all the old documentation on all coils and memory locations regardless. However, this doesn't seem to be the case.  Is there an easy way to delete only the element documentation so I can import a clean file?

[BobO]

Yep. Element documentation is stored in the <proj>.ESD and <proj>.ESX files. Deleting those two files will give you a clean element documentation database. Might want to back them up first though...just in case. 

[ATU]

I ended up deleting the duplicates manually. However for future reference, what is the "Delete existing" option on the import supposed to do?

[BobO]

I should know this...and don't ...but I suspect it means to delete records that exist for imported records. If there are records that don't overlap with imports, they would (and should) be left alone. Would one of the other fine Hosties that actually knows something useful like to chime in?

[ATU]

If that was the case, how does that option differ from the "merge with .csv priority" option?  Would that not do the samething?  I would think that the function of "delete existing" would delete all existing element documentation and replace it with the .csv file. Why else would you have that option?

[franji1]

Merge w/ .PRJ priority - if any elements have nicknames in both the project AND the .csv file, then use the one in the project
Merge w/ .CSV priority - same as above, except use the one in the .CSV file
Delete Existing - deletes the database files before importing so you end up with just what is in the .CSV file

[ATU]

Well, then something is not working correctly. I used the "Delete Existing" option and got duplicate nickname errors because there were nicknames in the csv file that were the same name for other Vmemory locations that were in the existing documentation. However those memory locations were not present in the csv file. Should that option not wipe the existing nickname database before adding the nicknames in the csv file?

[franji1]

Make sure you do not have duplicate nicknames in your source .CSV file.

Try importing it into a brand new project which has absolutely no documentation.  See if you still get the same error.

[ATU]

Franji,

This is really strange but only half way repeatable.  I have a program with over 2100 element nicknames. I imported the csv file to a new project (DL06). If I import the file again with the "delete Existing" Option checked, no errors. Delete the nickname at V6000 and put it at V6002. Then import the file again, you will get a duplicate nickname error.  You can do this several times and most of the time you will get the same error.  Put the nickname futher down, say V6040 and it goes through sometimes. Then try it again at V6002  and you may not get an error.    I can email you the CSV file if you want.

[franji1]

   hmmmm.  Yes, please email it to support@hosteng.com

We'll check it out.  Thanks!

[ATU]

Sent the file. But Now I can't get it to do it.

[franji1]

Delete the nickname at V6000 and put it at V6002.

Put the nickname futher down, say V6040 and it goes through sometimes.

Then try it again at V6002  and you may not get an error.

Are you doing these edits in
1. the DirectSOFT Documentation Editor (the big grid view)?
2. in the .CSV source file?
3. in the "Element Browser" (F9 dialog)?
4. or even a combination of the above???

[ATU]

I have since rebooted my computer (if this makes a difference) and it does it everytime now.
I have not changed the CSV file.
I open a new project for a DL06
Open the Documentation Editor (Grid view)
Import the CSV (Delete Existing option)
Go to V6000
Control X the Nickname
Go to V6002
Control V the Nickname
Import the CSV (Delete Existing option) you should get the error.

[franji1]

Whoa!  Able to duplicate it quite easily.  Thanks for working with us on this - hopefully it's an easy fix 

[ATU]

Great, for a while there I thought that I might start talking with a large furry rabbit.