All attributes extend SysAttribute class. So if you do a ‘find all references’ on that class you can find all of them. I realize this doesn’t give you a single documented place for all of them. But hopefully it helps some. I will keep an eye out for some more documentation. learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-ref/xpp-attribute-classes
'rsmTutsSysOperations*' means nothing to me. What kind of Domain Object are we working with, here? Sales leads? Invoices? I'd suggest a real world example for your next tutorial. Returning void and int doesn't really help people understand what's going on here. Neither are long, poorly named classes. We know what contollers and services are, so why clutter and further generify the names with a bunch of gobbledegook? But what's the domain model? Unknown. Poor design choice. Are we learning to run Select queries? Then why return just an int/void, when we could have objects? Really confused as to what X++ buys us, if anything at all. So far, it looks like yet another ORM. I'm probably wrong, but I still don't see the point of it, other than it likely being another proprietary vendor locked ERP system Microsoft sold to a bunch of gullible businessmen.
Kindly make a video on D365 new features and updates. How to read changes to the features and things to note before regression testing. Thank you.
thanks for the great content. do you know if there is a list of attributes available? without all the fun of debugging it :) ?
I believe there is… let me see if I can find it again and come back to this comment.
All attributes extend SysAttribute class. So if you do a ‘find all references’ on that class you can find all of them. I realize this doesn’t give you a single documented place for all of them. But hopefully it helps some. I will keep an eye out for some more documentation.
learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-ref/xpp-attribute-classes
'rsmTutsSysOperations*' means nothing to me.
What kind of Domain Object are we working with, here? Sales leads? Invoices?
I'd suggest a real world example for your next tutorial. Returning void and int doesn't really help people understand what's going on here. Neither are long, poorly named classes.
We know what contollers and services are, so why clutter and further generify the names with a bunch of gobbledegook? But what's the domain model? Unknown. Poor design choice.
Are we learning to run Select queries? Then why return just an int/void, when we could have objects?
Really confused as to what X++ buys us, if anything at all. So far, it looks like yet another ORM. I'm probably wrong, but I still don't see the point of it, other than it likely being another proprietary vendor locked ERP system Microsoft sold to a bunch of gullible businessmen.