Veristand Mapping issue

[meBaga]

I'm using Veristand 2017. I have a valid mapping for my SDF. When I'm opening the Project for first time, then go to SDF and view the mapping, it shows fine. At that point If I close the SDF even without making any change and re open it, then I'm getting this 1172 error. I have attached the error image.

Error details : 

Error 1172 occurred at Invoke Node Error calling method NationalInstruments.VeriStand.SystemStorageUI.WinFormsWrapper.TreeAliasBrowserWF.SetSystemDefinitionDisplayFilter, (System.NullReferenceException: Object reference not set to an instance of an object.)

Possible reason(s):

LabVIEW: A .NET exception occurred in an external assembly. For information about correcting this error, copy the following exception (in bold), and search the Microsoft Developer Network (MSDN) Web site or the Web for a possible explanation.
System.NullReferenceException in Mappings.lvclass:Apply Network Filter.vi->Mappings Dialog.lvlib:System Mappings Initialization.vi->Mappings Dialog.lvlib:System Mappings.vi->System Explorer Framework.lvlib:ButtonsMouseDown.vi->System Explorer.lvlib:System Explorer.vi->System Explorer.lvlib:System Explorer Wrapper.vi->System Explorer.lvlib:System Explorer Wrapper.vi.ProxyCaller

Any solution for this? because closing the project every-time is painful. 

[scotia673]

Thanks for the feedback - I agree that this is a frustrating problem. This is in fact a known issue (being tracked by Corrective Action Request 669410) and I anticipate that it will be addressed in an upcoming release of VeriStand. 

In the meantime, if you have to modify the system mappings, unfortunately closing the project is the only known workaround. If you simply need to view the mappings, you can instead select the System Mappings option in the item hierarchy of the System Definition window. 

[ZoeWang]

Hi,

My customer has also encountered this problem. Will this issue be fixed in Veristand 2018 or will be patched in the later 2017 version?

Thanks!

Best Regards,

Sha

[ZoeWang]

[update] I saw that this problem is still among the known issues of VS2018 . https://www.ni.com/en/support/documentation/bugs/18/ni-veristand-2018-known-issues.html#669410_by_Da...

So, my question is that does this issue will be fixed in the future version according to the VS product road map?

Thanks!

[tic.not.tock]

Hello Sha,

This is a CAR that we are currently investigating. I cannot promise that this CAR will be fixed in 2019 yet, but I do expect this to be fixed in future versions of the software. 

Thanks,

Andy

PSE