2019r2 changes a LOT of things.<\/p>\n\n\n\n
Some of the things it changed are subtle and search and replace may NOT be the best approach to updating these.<\/p>\n\n\n\n
For instance string method like Mid changed from being a 1 based offset for the starting position to a 0 based offset.<\/p>\n\n\n\n
If all you do is change mid<\/em> to middle<\/em> you will inadvertently cause an off by one error because the start is now 0 based not 1 based.<\/p>\n\n\n\n For instance<\/p>\n\n\n\n will give you different results in midString<\/em> and middleString<\/em>.<\/p>\n\n\n\n There are many other places where the offsets have changed from 1 based to 0 based so be careful updating your code. Make sure you examine all the parameters being used as well to avoid causing yourself a lot of extra work trying to hunt down those off by one errors.<\/p>\n","protected":false},"excerpt":{"rendered":" 2019r2 changes a LOT of things. Some of the things it changed are subtle and search and replace may NOT be the best approach to updating these. For instance string method like Mid changed from being a 1 based offset for the starting position to a 0 based offset. If all you do is change … <\/p>\nvar foo as string = \"1234\"\nvar midString as string = foo.mid(2,2)\nvar middleString as string = foo.middle(2,2)<\/code><\/pre>\n\n\n\n