Discussion

Cannot read property 'subLabel' of undefined

Forms Version 10

Updated May 10, 2019

posted on April 20, 2016

I'm getting a bizarre error on one of my forms.

The error is thrown when the form loads. I removed all the custom javascript I had on the form but that didn't help. I do have tables and connections tied to lookups, and the error seems to be related to that, but before I strip out all the lookup rules I figured I'd ask here.

I'm on 10.1.

0 0

Comments 2
Follow-Ups 1

replied on May 3, 2019

Has this issue been fixed in 10.4? I am having the same error with a lookup rule with a table when a lookup rule is set with a minimum range of 0. Any ideas on if a fix is coming or a proper workaround?

0 0

replied on May 10, 2019

Which version of Forms are you using? We fixed the issue Ege ran into with Forms 10.1. The issue we fixed is when use lookup to fill a field inside collection as new sets with collection option is range of sets and min is 0. The workaround for this issue is to change the collection option to "append sets to...".

0 0

Discussion 1

posted on April 20, 2016 • Show version history

Is this error appear when preview the form. If do, can you just copy the form, then remove all the lookup rules for the tables and check whether the issue persist?

0 0

View 7 previous replies

replied on April 20, 2016

Yes, I get the error when previewing the form.

I made a copy of the form and disabled the collection lookup rules one by one. Found the two collections causing the problem. Re-adding the rules did not fix it. The error is back.

Should I open a support ticket and upload the BP?

0 0

replied on April 20, 2016

Yes, please. And please provide screenshots for the lookup rules with the collections when open the support case.

0 0

replied on April 21, 2016 • Show version history

A case has been opened with Support to investigate; we'll update the thread when we have a resolution.

1 0

replied on April 25, 2016

This was discovered to be a bug in Forms, predating even latest release version 10.1. The error message is thrown in the browser console when using lookups with a collection configured to have a range of sets with the minimum number set to 0. Changing the minimum to, say, 1 will cause the error messages to not appear. SCR 143467 was filed to address this.

For others, note that (1) this is not an error message in a toast notification, it simply appears in the console of a browser's "Developer Tools" panel, and (2) no functionality related to the lookup rules, the collections, or their interaction appears to be lost. If you are receiving a visible error warning within Forms, or if lookup rules seem to be failing with collections, this is not the same situation.

2 0

replied on May 4, 2016

James, can we please have the fix included in the next service pack?

0 0

replied on May 5, 2016

Hi Ege, I added the related SCRs to the hotfix list for 10.1

2 0

replied on May 17, 2016

What is the timeframe for the hotfix you mentioned? We have a deployment coming up in June and we'd like to make it error-free since the form will be public-facing.

0 0

replied on May 17, 2016 • Show version history

We plan to release it in next couple of weeks(may be able to release it around middle of June)

0 0

replied on May 28, 2016

Does Forms 10 Update 2 contain this fix? I looked at the list but didn't see it.

0 0

replied on May 29, 2016

Hi Ege, Forms 10 update 2 is an update for Forms 10.0, your issue which reported with Forms 10.1 will be fixed with Forms 10.1 update 1, we are still working on it, It will be available in a few weeks.

0 0

Discussion

Discussion

Cannot read property 'subLabel' of undefined

Comments 2

Follow-Ups 1

Discussion 1

Sign in to reply to this post.