Find out the reason!

If you're sure the code base is the same then it must be that either that
(a) you are using different data
(b) (just possible) code is expecting the item to be populated before an async call completes and your connection is slower.

Either way, put a breakpoint on the original code and look at the stack trace that led to that situation.....

It's possible that your fix is a valid one - but you don't know that.


>I went ahead and fixed these errors in js file (added checks for variable defined) in these functions. So I am not getting these errors anymore.
>
>Still it's weird why nobody else was getting these errors with that wrong code?
>
>Also, what do you normally do in such situations when you're the only one getting errors in the code which is supposed to error. Do you try to find the reason or just fix them?
>
>Thanks in advance.
>
>
>>Hi everybody,
>>
>>We have a perplexing situation here.
>>
>>I've just downloaded the latest code with overwrite option, so I am certain (99%) that I am running the same code as other developers.
>>
>>Yet they are not getting JavaScript errors and I do when we open the exactly same form.
>>
>>I get the errors in both IE 11 and Google Chrome. The error itself does make sense to me
>>
>>TypeError: Unable to get property 'atId' of undefined or null reference
>>
>>(and it points to particular place in the code which has the following):
>>
>>

>>   $scope.filterAvailabilityTemplates = function (item) {
>>            return (item.hidden == false || item.id == $scope.currentItem.atId);
>>        };

>>
>>Obviously this code is supposed to fail if the $scope.currentItem is not retrieved yet.
>>
>>So I am wondering why would I be the only one getting these errors and not the rest of the team?
>>
>>I've added two attachments. If I trace the code, I can see that it goes to that definition and at that point the $scope.currentItem is not defined.
>>
>>Thanks in advance.