BP Deviation documented
Lak
I have a doubt.
Why //BP deviation documented is added in the display methods of Axapta
reports?
At what all places do we need to use this?
Axel Kühn
display methods (and edit methods also) can break your security setting.
Think on the following.
A user has access to Table A and not to Table B.
Table A has a display method which displayes data fromTable B.
If you use the dieplay method of Table A in a form or report, the user gets
access to the data returned by the display method and so gets access to table
B.
Please take a look into the Writing secure X++ code whitepaper.
There you can find a section about display and editmethods describing this a
little bit more in detail.
http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=5e050494-1613-4b3a-9363-d69d60c56877&displaylang=en
--
Sincerely yours
Axel Kühn (visit my Dynamics AX blog at: http://blog.ak-home.net)
Klaas Deforche
What Axel says is totally right.
More about the comment line: (//BP deviation documented )
When you do the kind of things Axel describes, the AX debugger will make you
aware of it in the debugger output window. You'll see best practice
deviations. When you're sure your code is secure, you can put "//BP deviation
documented" above the line the debugger is complaining about, causing the
best practice deviation message to disappear.
Regards,
Klaas.
------------------
http://www.artofcreation.be