Error 1124 After modifying a workspace object

[SRML1124]

I'm hoping someone can help me with an issue I am experiencing modifying workspace objects in Veristand please?

I don't believe I am trying to do anything overly complicated and in fact it is covered by option 2 of this link https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x4QfCAI&l=en-US -  "2.Changing the Appearance of a Workspace Object". 

One of the problems I am having is that I am using LabVIEW 2015 and Veristand 2014. If I simply modify an existing workspace item and save with a new name, Veristand gives me an error stating that the object isn't compatible when I try to drop it on the workspace. 

So I used the option to save as an earlier version, but now I am getting the following error message when I try to drop it on the workspace:

I have tried a few things but to no avail, so any help would be greatly appreciated.

Thanks Si. 

[Tepig]

Hi, I belive your software combination is wrong.

If you are using LabVIEW 2015, you should use VeriStand 2015.

Also using LabVIEW 2014, use VeriStand 2014.

See this compatibility table.

https://www.ni.com/en/support/documentation/compatibility/22/veristand-model-generation-support-and-...

[Tepig · Accepted solution]

This is because VeriStand 2015 uses VIs which is compiled in LabVIEW 2015.

If you edit VIs with LabVIEW 2014, the compatibility is lost, VeriStand cannot call those VIs.

[SRML1124]

Ah okay, I was worried that would be the root cause. 

So saving my VI (LabVIEW 2015) as an earlier version (LabVIEW 2014) isn't a viable solution? 

I suppose I will stick with the standard workspace objects.

Thanks Si?

[Tepig]

Saving earier version may be a solution but i have no confidence. I haven't tried it : (

Why don't you use a compatible software?

[Tepig]

Hey, did saving VI as an earlier version solve the problem?

If you could have solved, plz make this thread resolved by setting "mark as solution".

[SRML1124]

Unfortunately saving as an older version did not work, but I now have a access to LabVIEW 2014, so I have got around the problem. 

Thank you for your help.

Si