Expand my Community achievements bar.

SOLVED

Add page button throwing error

Avatar

Former Community Member

I have a "add page" button on my form that is suppose to create a new instance of both page 3 and page 5.

I got it working in two different fashions:

FormCalc

Page3.instanceManager.addInstance(1);

Page5.instanceManager.addInstance(1);

Javascript
Page3.instanceManager.addInstance(true);
Page5.instanceManager.addInstance(true);

In both cases a new instance of page 3 & 5 are added to the form and everything functions as expected.

The problem is that right when the button is pressed I get an error message

LC_badValue_Error.JPG

It appears to me that it is trying to set the value of 'initial' which is a child element of 'occur' which I assume has not been initialized but I am having a heck of a time figuring out how to peroperly do it.

Thanks in advance for any help.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Would need to see the form ...can you send it to

LiveCycle8@gmail.com ...include a description of th eissue with the email.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Would need to see the form ...can you send it to

LiveCycle8@gmail.com ...include a description of th eissue with the email.

Paul

Avatar

Former Community Member

pguerett found the answer.

Both my pages contained tables that were set to have 18 rows each.  The problem stemmed from the first page, whose table was defined to have a min rows of 18, a max rows of 18 and an initial row count of 18.  By unchecking the initial rows and leaving just the min and max everything is working great.

Thanks pguerett

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----