LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Meaningful error message in case build path is too long for the application builder

Status: Declined

Created Bug 1067802 to track the issue with unclear error reports when build paths are too long.

Please create a meaningful error message in case the application builder errors due to long path names.


The error below was ultimately fixed by shortening the output path in the build spec. It took me however more than half a day of fiddling around with alternative solutions to reach my end goal (


While explaining it to my colleague it hit me that the build output path could be too long, shortened it, built it, deployed it, and it worked.



Build error.PNG

André (CLA, CLED)
Active Participant
Status changed to: Declined

Created Bug 1067802 to track the issue with unclear error reports when build paths are too long.

Christina Rogers
Productization Lead, LabVIEW R&D
Active Participant

Hi Chistina,


The declined status seems a bit contradictory with the bug ID in it. But I recon it is part of something bigger related to the application builder in general?


Thanks anyway for creating a bug report. 

André (CLA, CLED)
Knight of NI


The Idea Exchange is supposed to be for new features.  Quite a few ideas are actually considered bugs and therefore closed, but documented in NI's bug tracking tool.

There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Active Participant

Hi Crossrulz,


Thanks for the explanation, I thought it must be something like that.


Well it's all in the eye of the beholder 😉 For me it would be a useful feature, but you can also consider it a bug. All depends on whether it is or was a requirement inte first place.


Any way I'm happy it's on a to do list and hopefully a small into that can be scheduled into the next release.


Kudos to NIs quick response.

André (CLA, CLED)
Proven Zealot

> Kudos to NIs quick response.


You're welcome for the response, but I want to set your expectations at the right level: We can acknowledge an issue and still not get it fixed for quite a while, or ever. There are a lot of competing priorities. Moving this to "bug" does put it in the higher priority consideration bucket, but it isn't necessarily a commitment to fixing it.

Active Participant

Hi AQ,


I have the right expectation. I know the amount of work that you guys have is tremendous. For me it's enough for now to know that it's on a radar and will not be forgotten or closed without further consideration.


Sometimes you guys deserve a celebration for the improvement in feedback to the community over the past 5 years or so.


Keep up the good work.

André (CLA, CLED)
Proven Zealot