NEWUNIT in part name field in Database view.

I can not work out what is causing this....

Load the database and there are a number of units showing NEWUNIT. I know these are wrong double click and the Part name is correct. I thaught it was just NEWUNIT. but what I am finding is that there are a number that show old labels I had one called BATH and changed to BATHHI quit and reload and the the partnumber shows BATH. double clik on it and it shows BATH1

I find this wierd as why would you be saving the old partnames ?? I can not work out where it is reading them from. I checked the XML file and the old name is stored here (ie BATH) Also the other name BATHHI is stored here too !! (see below)

Why are you storing the UnitType Twice ?? why does it not update both locations ??

The network view is fine..

Charles

 

Sorry about reposting the same thing 5 times. The XML example was being eaten buy the Forum software..

Attached is the example as an image.

Trying to work out how to delete the other posts

 

Hi Charles,

Thanks for the detailed post.

The "PP" parameters are ones that end up in the unit. The first UnitName is a reference to a database parameter only.. There's possible future scenarios that might see these being different, but it would appear you've uncovered an anomaly in the way they operate at the moment.. will research it a bit and get back to you.

 

Hi Charlie,

You could edit the XML file with Notepad etc.. but better to wait till the software gets updated, a mis-edit could leave you high and dry..

Defect # 4167.

 

Duncan,

Are you impersonating me !! or a bug in the forum software !!

I also found the problem happens whe you scan a virgin network with tool kit and copy all devices to database. The PP name gets updated but the Unitname xmlns = "NEW UNIT".

Charles,

 

That is bizarre.. looks like a VBulletin bug!

Thanks, we're on top of this now..

 

install 3.05
admincp/import&maintenance/repair&optimize tables

Should do the trick.
cheers

 

Despite it saying 3.0.4 at the bottom, the necessary critical patch files from 3.0.5 are installed.. will give the repair and optimise a shot

 

Heheh,
lol, good to see you are on the job Duncan. You might want to do a backup of the database and then close the forum to general public access while you optimize. Some erroneous errors to database structures similar the one presenting have been known to appear if you don't close the db, or so I've heard.
cheers

 

Thanks Ross.. already ran the optimise without closing down access (whoops ).. Didnt fix the problem though.. will go hunting thru the tables at some point and see what went wrong.

 

Newunit

Newunit.
I have found that when i have added some new unit to a project that in toolkit (1.1.4) they show as "newunit" but as soon as you click the partname field they changed to the correct name. If I then save to database and restart toolkit they come back as newunit again.

dave

 

Hi Dave,

This has been resolved for the next release.