# \[Bug-Resolved\] commented out value still errors in script

**URL:** <https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088>\
**Category:** Ignition Early Access\
**Created:** [November 27, 2018, 6:49pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088 "2018-11-27T18:49:01Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![brian.mills](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brian.mills/32/6348_2.png) [@brian.mills](https://forum.inductiveautomation.com/u/brian.mills)\
**Post date:** [November 27, 2018, 6:49pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088/1 "2018-11-27T18:49:01Z")

</div>

1. List item

When I go to the custom property for the root container in perspective, I ave commented out other attempts, but I still get an error in the wrapper log…

1. List item  
Not expecting to have an error in the wrapper log for something commented out…

2. List item  
To expose this I was watching in the wrapper log and kept seeing the “line 3” error that object has no attribute ‘scanBarcode’. Deleting the # commented out rows or putting them in triple quotes seems to resolve this…

Potentially not a bug? Syntax for commenting out in Perspective needs the triple quote instead?

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/ecba26c92ff09bea5f88dfeebe69dd48877996fb.jpg) ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/4c0a95a84f8173eff00d8b2d4588676a6ce5c3d7.jpg) ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/77d4b00ad8078652f8a74c552b9db50f6d3f405a.jpg)

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [December 11, 2018, 10:16pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088/2 "2018-12-11T22:16:34Z")

</div>

Is this still happening? Perhaps you could export the view in question and attach it here.

---

<div class="post-metadata">

**Author:** ![brian.mills](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brian.mills/32/6348_2.png) [@brian.mills](https://forum.inductiveautomation.com/u/brian.mills)\
**Post date:** [December 11, 2018, 10:40pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088/3 "2018-12-11T22:40:26Z")

</div>

I was seeing this on multiple views, anytime a hash tag comment (or ctrl+/) was used.

> [@brian.mills](#):
>
> To expose this I was watching in the wrapper log and kept seeing the "line 3" error that object has no attribute 'scanBarcode'. _Deleting the # commented out rows or putting them in triple quotes seems to resolve this_...

Although I can still attach a .JSON if you would like

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [December 11, 2018, 11:17pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088/4 "2018-12-11T23:17:47Z")

</div>

A JSON for the View would be helpful, as I’m not able to replicate this with the following setup:  
 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/c48e87f6b30680f5b332766ee0fbc64de56ae808.png)

---

<div class="post-metadata">

**Author:** ![brian.mills](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brian.mills/32/6348_2.png) [@brian.mills](https://forum.inductiveautomation.com/u/brian.mills)\
**Post date:** [December 12, 2018, 2:17pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088/5 "2018-12-12T14:17:32Z")

</div>

In attempting to duplicate, I am unable to have it throw the same error… so I am guessing it must have been fixed with one of the nightly builds since I had this issue

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [December 12, 2018, 3:07pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088/6 "2018-12-12T15:07:31Z")

</div>

Or perhaps the script wasn’t saved after the comments were put in place? Either way, I’ll close this thread for now. If you encounter it again, please let us know.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [December 12, 2018, 3:07pm UTC](https://forum.inductiveautomation.com/t/bug-resolved-commented-out-value-still-errors-in-script/21088/7 "2018-12-12T15:07:48Z")

</div>

Closed on December 12, 2018, 3:07pm UTC


