From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Write Delimited Spreadsheet.Vi error

Solved!
Go to solution

I used Write Delimited Spreadsheet.VI in a program and opened the vi and added one terminal and saved it. After this the VI is inactive and if use this in any program it says polymorphic VI does not contain SubVI's. What may be the problem?. How can i get back to old settings?

0 Kudos
Message 1 of 11
(4,985 Views)
Solution
Accepted by topic author skem

@skem wrote:

I used Write Delimited Spreadsheet.VI in a program and opened the vi and added one terminal and saved it. After this the VI is inactive and if use this in any program it says polymorphic VI does not contain SubVI's. What may be the problem?. How can i get back to old settings?


You do this by not futzing with a shipping VI in the first place!!!  Do a repair and if you want to make a change, copy it somewhere first and make changes to the copy.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 11
(4,976 Views)
Solution
Accepted by topic author skem

Did you really modify a Vi from VI.lib? That's a really bad idea!

 

This VI is polymorphic, meaning it is a collection of VIs where the correct one depends on what you wire to it (array of strings, floating point, or integers). You only modified one specific instance. (details)

 

(If you really overwrote a system VI, you should probably reinstall LabVIEW and never do it again.)

0 Kudos
Message 3 of 11
(4,970 Views)
Solution
Accepted by topic author skem

Hi skem,

 

general rule: NEVER fiddle with VIs supplied by NI in the vi.lib! Use them just the way they are!

 

As Blokk said: when you want to alter them you need to create a copy of them. Use that (altered) copy instead of the original…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 11
(4,968 Views)

Besides the kind of issues you are experiencing right now, what happens when you upgrade to a new version of LabVIEW?  What happens if you open the project on another computer?

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 11
(4,937 Views)
Solution
Accepted by topic author skem

Although, ironically, within the vi itself there is a comment block

"Array to Spreadsheet separates rows with EOL characters.  If your spreadsheet application needs different terminators, use the Search and Replace from the String palette (or something equivalent) at the output of Array to Spreadsheet String to modify the string." indicating, perhaps, that the original programmer wasn't clear on the general prohibition against mucking with vi.lib VIs.   Mixed messages to the newer users.

 

But as the previous posts say, messing with the built in VIs is not a good idea, you may break things you don't even realize you have touched, and if there are other developers, if you don't "break it" you may change a function's performance in ways that aren't obvious to the next person (or even you, a year from now, when the "Help screen" info differs from the VIs "new" functionality. Even copying to a new location to make your on version has risks, if you don't do it correctly then things the original might be linked to may broken.

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 6 of 11
(4,922 Views)

Of course if you just added a terminal and did not change anything else (eg. code), just remove the terminal and re-save again. I still would probably not trust it. What kind of terminal did you add and why?

0 Kudos
Message 7 of 11
(4,913 Views)
Solution
Accepted by topic author skem

@skem wrote:

I used Write Delimited Spreadsheet.VI in a program and opened the vi and added one terminal and saved it. After this the VI is inactive and if use this in any program it says polymorphic VI does not contain SubVI's. What may be the problem?. How can i get back to old settings?


The safe way to do this is to create your own sub-VI, "My Delimited Spreadsheet VI", populate it with terminals as you see fit, and use its Block Diagram to wire your terminals to the (unaltered) terminals of the NI Write Delimited Spreadsheet VI.  This technique is called "Having Your Cake and Eating It, Too".

 

Bob Schor

Message 8 of 11
(4,909 Views)

Thanks to all for your quick responses. I did not try repairing it instead removed the whole package and reinstalled. Now the VI is working fine.

Message 9 of 11
(4,873 Views)

No. I just added terminal and did not assign with any function. I tried deleting thereafter. Its not of any worth.

0 Kudos
Message 10 of 11
(4,869 Views)