Bug Javascript Function parseInt

Not so long ago I encountered a problem with the parseInt JavaScript function. In some cases the parseInt returns an incorrect value. For example, parseInt("08") results in 0 instead of 8 and parseInt("09") also results in 0 instead of 9.
Apparently the reason for this is because the zero in front is trying to tell the browser that this is an octal number, and "08" and "09" are not valid octal numbers.
With parseFloat I didn't have the problem. So to "fix" the problem, I used the following: parseInt(parseFloat("string value"))

Please note that this "bug" only happens when the value being checked is a string and the string starts with a leading zero.

Kevin Dosseray

Comments

Post a Comment

Popular posts from this blog

New CRM 2011 VM on PartnerSource

Microsoft released a Virtual Machine for CRM 2011 on PartnerSource. The VM includes CRM 2011, SharePoint, Exchange, Outlook client and XRM scenarios such as portals. Please note that the VM must be run on a 64bit server with Hyper-V. You can download it here: https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID={060C9677-229D-49E1-9F00-95E56D9F1657}&NRORIGINALURL=/partnersource/deployment/methodology/vpc/MSD_CRM2011VirtualMachine&NRCACHEHINT=Guest&wa=wsignin1.0
Read more

BizTalk Error: The adapter failed to transmit message going to send port

I was doing the following: in my orchestration I was sending a message to a custom WCF service. The message was build dynamically (custom .NET class) and passed to a send port configured for a WCF service. All looked fine (and compiled correctly) until I ran the application: I received the "The adapter failed to transmit message going to send port" error. After some investigation it turned out I received the error because the type of the message I was sending through the send port did not match with the type the WCF expected at the other end. After updating my message with the correct namespace, all worked fine again.
Read more

CRM 2011 together with the Scribe Adapter for CRM 4.0

So you upgraded your CRM 4.0 to CRM 2011, but still use the CRM 4.0 Adapter in your Scribe integrations (Scribe Adapter for CRM 2011 will be released the end of March 2011). No worries: if you don't use hosted CRM, your integrations will still work. The Scribe Adapter for MSCRM 4.0 works with all CRM 2011 entities that existed in MS CRM 4.0. So as long as you don't use new CRM 2011 functionality (Connections, Sharepoint, Auditing...) in your integrations and it is a CRM 2011 On Premise or a CRM 2011 online version, you can use the MSCRM 4.0 Adapter without any problems. As we all know, the old MSCRM 4.0 endpoint is still accessible in CRM 2011, so the compatibility sounds logical. The reason that you can't use the adapter in a CRM 2011 hosted environment is because of the Claims Based authentication used in this environment. The authenticaton is not supported by the old adapter. This will be no problem with the new CRM 2011 adapter. Please note that you will need a...
Read more