Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet

Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Thursday, March 25, 2010

Dynamics AX X++ Team looking for input

Last week, the Microsoft Dynamics AX, X++ Team posted on their blog that they are looking for community input. Being out last week, I did not pick up this, and just saw it today.

If you have seen this, and already left your thoughts great! However if not, please visit the following direct link.: More help needed from community: Do you rely on string truncation?

From the post.:
"Previously the X++ language allowed the LEFT and RIGHT keywords on definitions of string variables. That is no longer valid X++. However, we still allow specifying an explicit string length. The X++ language runtime implicitly does string truncation on assignment, both directly and when passing parameters. Consider the following example:

str 5 s;
s = ‘124567890";

The resulting string will only contain the first 5 characters, i.e. ‘12345'. Normally the user would not explicitly provide the length of the string in this way, but the behavior is exactly the same when using an extended type that has a particular length. One example is the SysGroup type, that is defined as having length 10 in the properties for the extended data type. If you run

SysGroup g = ‘1234567890ABCDEFGHIJ";
print g;

You will only get the first 10 characters printed. The remaining ones are lost to truncation."

"The question for you to answer is: Do you rely on these semantics in your code? Would your code run well if all string types were equal and unbound? Do we need to muddy the waters for IL by introducing the same behavior in IL?"

My answer to this is that the IL code should not be made to operate like the current Interpreter does. Don't make the generated MSIL code operate against the nature of how the MSIL code works in every other .Net langauge.

Truncation should only happen at the database level, and if true truncation is needed for some kind of validation, then it should be performed with strlen() and substr() calls.

That's my two cents, what's yours? Make sure to let the X++ team know!

"Visit the Dynamics AX Community Page today!"

Labels: , , , , , , ,


Post a Comment

<< Home

Copyright 2005-2011, J. Brandon George - All rights Reserved