Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
1. If I use a limited user to write in Item Journal Line (T83) and then this same user posts this line, would this work? (assuming that codeunit 22 -Item Jnal. post line- will write in more than 3 extra tables).
2. If I use a limited user, do I have to specify somewhere which 3 tables he/she can write on, or this limitation is only valid in each different transaction he/she may perform?
Check out appendix a from license guide.
if the used tables when Posting are on that list, everything is fine.
I hope this helps. If my response has answered your question, please click Yes to verify next to "Did this answer your question?"
Best way would be only write to item journal from external app with limited user without Posting the lines. Create a Job queue entry which is Run by a full User and posts periodically these Job journal lines.
That would probably upset Microsoft.
On page 4, the same paragraph I cited in my earlier response also states the following:
"Transactions created by a Limited User are not considered indirect write access if (i) they are needed by a Full User as in an input to perform their job function and (ii) transactions are processed individually (not in a batch)."
In a way, I can see how a Limited User filling out the Item Journal would fall under clause (i) above. But, I imagine it will be posted as a batch, and thus will go against clause (ii).
Unless your Limited User populates one Item Journal entry at a time(??)
If you work for a Microsoft Partner, your best bet would be to reach out to your Microsoft Partner Technical Advisor for an official clarification.
As aj ansari correctly describes it's always a mess with limited users. The formal restrictions are quite hard and you need in the end a license attorney if you want to use it correctly/legally. But ... in all cases where one wants to use LU the Situation is not clear and needs clarification with microsoft. I assume MS has defined that deliberately complicated in that way. So MS can handle that the hard way, so in the end LU is not usable at all ... or handles that not so hard and you can use LU although you use it maybe not 100% correct.
i agree with Jonathan, "Job queue posting" is a good solution also suggested by Microsoft.
That would not much upset Microsoft as in good old days the option was to access the SQL database directly or via some web-based interface bypassing the application as such :-), which was indeed upset for Microsoft. Now they at least have some limited license sales.
I know you mean well Alexander, but as a Microsoft Partner, it is very important to make sure that we're careful about how we answer a license question and do not inadvertently encourage misuse of a license.
Indeed! This is what I'm exactly telling.
In the case when customer is coming to you and telling "I have 300 operators of call center who perform only one action of filling in only one document", under earlier license model this might mean he needs to buy 300 user licenses, which is of course stupid as he would not use 99 percent of functionality he had paid for.
Exactly for this type of cases Microsoft had introduced limited license user into licensing model, in order to give customers opportunity to be loyal :-).
Business Applications communities