Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

drop down issue.

Avatar

Level 3

Hey Guys,

I'm having some issues with the form at the below link.  I want the first dropdown to fill the second drop down which works but the unitPrice field isn't populating by the second dropdowns choice and what is in the wCSMMonth field.  I'm just about bald on this one lol

http://www.shingleme.com/CostWorkSheetTest_Pauls.pdf

Justin

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Your wCSMMonth field does not have a value. You have a caption set to 150 but it has no value. I suggest getting rid of the caption then setting the field to readOnly then the Value property will become active and you can put the default value in there.

paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Your wCSMMonth field does not have a value. You have a caption set to 150 but it has no value. I suggest getting rid of the caption then setting the field to readOnly then the Value property will become active and you can put the default value in there.

paul

Avatar

Level 3

I should have just redone the whole FORM at this point.  I didn't even think about the caption.  I was so stuck on the fact that the js wasn't working properly I didn't even think about the actual field again as I knew I changed the field from text to numeric so I figured that part was good.  Thank you again for your help.  I'm learning a ton on here and appreciate all the feedback and support along the way.

Justin

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] ----