ng-model binding not updating

Question

I have some models being updated from a look-up. It is the 1st line that's not updating (but the other models are updated correctly). I tried wrapping it in an $apply but that made matters worse:

 function mapRequestorToForm() { //PrimaryCtyhocnOrInnCode binding not updating //$scope.$apply(function() { dmpe.form.PrimaryCtyhocnOrInnCode = dmpe.requestor.primaryInnCode; dmpe.form.hotelName = dmpe.requestor.hotelName; dmpe.form.requestor = dmpe.requestor; //}); }

Here's the input element. Funny thing, the pre element is displaying the correct value.

 <label for="primaryCtyhocn">Primary Inn Code/ CTYHOCN</label> <input type="text" id="primaryCtyhocn" name="primaryCtyhocn" ng-model="dmpe.form.PrimaryCtyhocnOrInnCode" class="form-control required disabled-bg" disabled placeholder="Primary Inn Code/ Ctyhocn" ng-minlength="5" ng-maxlength="7" required /> <pre>PrimaryCtyhocnOrInnCode: {{dmpe.form.PrimaryCtyhocnOrInnCode}}</pre>

this one is updated correctly (line 2 of the map method, using the same source object with similar disabled attributes:

 <div class="col-md-4"> <label for="hotelName">Hotel Name</label> <input type="text" id="hotelName" name="hotelName" ng-model="dmpe.form.hotelName" class="form-control required disabled-bg" disabled placeholder="Hotel Name required" required /> </div>

What's up with the disabled attribute? It feels like your code may have some JavaScript executing behind the scenes that's trying to set the value of that input text box and it's failing because of that attribute. — Mike Perrenoud
– Mike Perrenoud, Commented Jun 18, 2015 at 17:18
Just a silly guess..did you missed here dmpe.requestor.primaryInnCode should be dmpe.requestor.primaryCtyhocnOrInnCode & are you sure,if it is primaryInnCode. does contain value? — Pankaj Parkar
– Pankaj Parkar, Commented Jun 18, 2015 at 17:21
@MichaelPerrenoud fields are populated for the user based on an object returned from a look-up. For this use-case it is not editable but can be given the correct role. The other disabled input fields are updating correctly — Will Lopez
– Will Lopez, Commented Jun 18, 2015 at 17:41
@pankajparkar thanks but that is the proper field. It is an object returned from a look-up. The pre element is displaying the correct value so the model has the value but the binding isn't working — Will Lopez
– Will Lopez, Commented Jun 18, 2015 at 17:43
Is it possible that the value you're displaying does not meet the minimum length requirement? — Mike Perrenoud
– Mike Perrenoud, Commented Jun 18, 2015 at 18:41

Will Lopez · Accepted Answer · 2015-06-18 19:10:51Z

In case someone else runs into this and their brain is failing them as mine did. It was an issue with the incoming data, it failed the max length constraint. Thanks to Michael Perrenoud!

Collectives™ on Stack Overflow

ng-model binding not updating

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related