web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Roles behaving differe...
Microsoft Dynamics GP (Archived)

Roles behaving differently in diferent companies

(0) ShareShare
ReportReport
Posted on by Ian Salisbury 410

We have a viewonly role with the following tasks: INQ_PURCH_002*, INQ_PURCH_004*, INQ_SALES_008*, LIST_PURCH_001*, and LIST_SALES_001*

When a user has only this role assigned, in both companies, they can get to the "Purchase Order Inquiry Zoom" window just fine.  The odd part is that in one company they can print, in the other they get a popup saying "You don't have access to this document type".

I'm seeing the same behavior with different users in different test environments.  All I could see in DEXSQL.log is that it works in one company and the error is presented in the other.  The records in the view SY10000 look identical between companies.  I even tried rebuilding store procedures in a test environment.

Can anyone spot what I'm missing?

TIA!!

*This post is locked for comments

I have the same question (0)
  • Ian Salisbury Profile Picture
    Ian Salisbury 410 on at

    Forgot to add... Power Users can run the reports from both companies, so the mechanics of it is working.

  • L Vail Profile Picture
    L Vail 65,271 on at

    Are you OK with this issue, or is there still a question?

    My first glance would be to check each user's security - something is different. Of course Power Users can do anything. Are some of the users in question Power Users?

  • Ian Salisbury Profile Picture
    Ian Salisbury 410 on at

    The difference isn't between users, it is between companies.

     A user with the viewonly role, and only the viewonly role, in both companies, can run the report in one company and not in the other.

    Thanks for the response :)

  • Sudin B Profile Picture
    Sudin B 370 on at

    Ian, One option to consider is to Copy the security for that user from the company with no issues to the company with the issue. You can use the "Copy" function in the user security window.

    Best regards,
    SB

  • Ian Salisbury Profile Picture
    Ian Salisbury 410 on at

    Thank you Sudin, but that did not help.  I was going to be worried if it did as I mentioned in my first post that there were no differences in the SY10000 view.  This is very puzzling.

  • Sudin B Profile Picture
    Sudin B 370 on at

    Ian, have you tested by creating a brand new user id? does it happen to new user as well? Also, you could consider running GP's maintenance for Advanced Security and Checklink on Security Tables.

  • Ian Salisbury Profile Picture
    Ian Salisbury 410 on at

    Same behavior seen with completely new users.  No errors found with checklinks on advanced security, No errors found with checklinks on system series.

    I noticed the following in SQL profiler...

    When I click the print button in the good company, it looks up

    SECRESTYPE = 2 and SECURITYID = 784

    That is INQ_PURCH_004*          

    When I click the print button in the bad company, it looks up

    SECRESTYPE = 400 and SECURITYID = 301

    Which is TRX_PURCH_001*          

    If I add TRX_PURCH_001* to the ViewOnly role, it can print the report. (Not a solution)

    Why are the lookups different when clicking the same button from the same workstation in different companies?  Could we be missing a module in the bad company?  GP Utilities didn't notice when I upgraded to the lastes SP.

     

     

  • Sudin B Profile Picture
    Sudin B 370 on at

    Ian, following are few additional comments on this:

    1) This seems to be related to the security for "Document Access". You could try checking the "Print Operation Access" report for "Document Access" in the Security Task Setup window. That should show which company has access for each document type and user.

    2) Based on the task IDs that you selected for the "ViewOnly" Role, GP should not have allowed you to print the PO even in the good Company. what do you think?

    3) I am not sure regarding the missing module either.

    4) One workaround to consider would be to create a new Task ID with "Document Access" for the Purchasing series and selecting all the types of POs. And then assigning that Task ID to the ViewOnly Role.

    5) Also, just to make sure, double check the Company Setup window to make sure "Security" is checkmarked in both companies.

    6) Do you have access to any other functions of Task ID "TRX_PURCH_001*" in the good company? besides the PO printing function? For example, are you able to enter a new PO in the good company?

    7) For the POs that you tested, is the PO Type same in both companies? "Standard", "Drop Ship" etc?
  • L Vail Profile Picture
    L Vail 65,271 on at

    Good thinking! The error did say 'document type' didn't it :)

  • Ian Salisbury Profile Picture
    Ian Salisbury 410 on at

    1 and 2 - Yes, the deeper I look, it looks like it shouldn't work in either company. The reports show no differences between the two companies, and expected differences with other companies.  ie, it shows that the same users I have been testing with should be able to print these documents in companies where they are power users.

    4 - Yes, that will get the needed access to the right users, but now seeing that it shouldn't be working at all, we have a much bigger issue.  Being able to print something they don't have rights to is not good for SOX compliance.

    6 - I haven't tested all functions, but no, the view-only users cannot add POs

    7 - Yes, all POs have been 'standard'

    Thank you so much for your help, since I have essentially been looking at this backwards, I may have missed something obvious in the 'working' company.  I'll start from scratch and respond to this thread in a day or two.

     Thanks again!

    -Ian-

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans