06-07-2021 09:59 AM
I've run into a problem on loading datasets into the Data Portal in DIAdem 2021 where the filename is automatically set as "NoName" - in previous versions, the file name (Data.Root.Name) would always be the name of the file that was dropped into the Portal. For example, if I opened a file named "testingFile_123.tdms" in DIAdem 2020, Data.Root.Name would be testingFile_123 by default.
In DIAdem 2021, loading the same file would yield Data.Root.Name = NoName. It has caused unexpected results in some scripts that would automatically save results based on the filename; since the filenames are now all NoName, it overwrites results and I'm left with just the last file. I haven't been able to find anything online about this yet - have I missed a setting somewhere that changes this loading behavior?
Solved! Go to Solution.
06-08-2021 08:18 AM
Hello AnscombesQuartet,
I tried to reproduce this problem, but on my side it works fine.
I have started DIAdem 2021 load a file and then run
msgbox data.Root.Name
In all cases the name of the file (without extension) is shown.
Greetings
Walter
06-08-2021 08:33 AM
Hey AnscombesQuartet,
Can you post an example TDMS file that shows this behavior for you in DIAdem 2021? Also, what operating system and localization language are you using? Do you perhaps have any load event code configured to run in that DIAdem 2021 instance you're using?
Brad Turpin
Principal Technical Support Engineer
NI
06-09-2021 08:19 AM - edited 06-09-2021 08:21 AM
Literally any data loaded has this behavior. This includes all TDMS, TDM, xls, xlsx, Dat, DatX, and csv files; for a concrete specific instance, loading the Example file included in a standard DIAdem install has this problem.
I'm running Windows 10, v2004, build 19041.985, experience pack 120.2212.2020.0. Localization is all in default English.
I have a script that runs on initialization that populates some custom toolbars. This same script runs on initialization on DIAdem 2020 with no problem, and the problem persists in 2021 when that script is not set to run on startup.
Edit: I forgot to mention - I went through the repair option in the NI package manager (and then rebooted), which did not fix the problem. I then uninstalled v2021 through the package manager (then rebooted), then reinstalled through the package manager (then rebooted). The problem remains.
06-10-2021 07:05 AM - edited 06-10-2021 07:07 AM
Solution found. I realized that I probably misunderstood your question about load event code, so I checked my Settings/Navigator, and had the idea to compare that to the Navigator settings from my 2020 instance. In the 2021 instance, I changed the DataFinder loading behavior/Property inheritance level from "Move to loaded level" to "None," and now Data.Root.Name is loading as expected.