I am trying to create a rule for when a user of a group that I have created called technicians can only see their scheduled appointments but the admin user must see all the appointments of all the technicians. It's not working for me.
As you can see in the attached images, there is a user eduardo tecnico that is associated with the field combination of resources and effectively shows me the appointments associated with it, but when I log in as admin it does not show anything, no appointment. And if I activate line 7 of the code, it shows all the appointments for the admin and for the technician, which is not what I am looking for, what can I do? what am I doing wrong?
Attached images:
Rule
Admin view
Technician view
I have tried modifying the domain_force in many ways with no positive results.
Related
I've just started looking at permissions and I'm trying to work out exactly what permission allows the user to create new customers. I've downloaded the NetSuitePermissionsUsage_2022.1.xls spreadsheet, and it looks to be the Customers permission. But I can't find where it shows that in the actual 'Usage Description' column. It shows 'Allows usage of the New Customers task', but I can't find anywhere it actually says what the 'New Customers task' actually is. It doesn't look like it's actual creation of new customers, because you only need View level of the Customers permission to have it, and View level does not allow creation of new records.
So if I'm right, and the Customers permission is what allows the user to create new customers, where does it say so in the document? Or elsewhere?
Our requirement is for specific user we need to check what events he performed.
Lets say for user John we need to check if he able to find out filter feature from app etc.
On Fabric I can see its shows event and unique users, but its not showing their username, userid etc.
So is there any way to do this?
Thanks.
Mike from Fabric here. With the Fabric dashboard, there is not a way to track a user across crashes and events. You can however, add custom logs, keys and user identifiers to exceptions or logged errors and can then search on those values.
Is there a way I can restrict a field in TFS for the creator of the ticket once the ticket reached a particular status? For example I have created ticket 123 in TFS and the assignee of the ticket set it to In Progress status. I as the requester should not be able to edit the Issue Description field since the ticket is already being worked on by the assignee.
There is no way to limit access to a different specific user per work item state.
You can add limited for a Group or Individual for a particular state, but it would always be the same individual.
If this problem is not rife then you can simply add a notification for the creator when the work item changes, you can for to the bits that you want, and have users self police.
The issue I'm having in Dynamics CRM 2013 is the ability to assign activities or appointments to a team and have those cascade downward into individual users. The end goal here would be after assigning a lead or activity to a team, the users within that team would receive notifications, emails, etc. and those records would integrate with their 'my' sections of CRM.
The issue I see with this is that only 1 'Owner' can be set for a new record in all areas of CRM, and the 'my' sections are based off of the Owner. Therefore the users within the team won't be notified.
We are currently using a service to pull from an existing database and populate CRM, assigning new leads to a Team which contains multiple users.
Does anyone have a recommended method to do this?
Thanks for your time.
Either give the users a view of "Leads owned by Teams of which I am a member" or possibly use Queues, which are pretty much designed for the scenario you describe.
New items assigned to a Team will be added to the Team's Queue. Users can see all Queue Items not yet being worked on (from all Queues they have access to, including all Teams they are members of). A user can "work on" an item to show they are dealing with it so it no longer appears in this list of items to be worked on, and instead appears in their own list of items they are working on. A user can either complete the item or 'release' it back into the queue.
Queues can contain items of different types, eg Leads, Tasks, Cases etc.
I'm trying to create a register, in a way, so that users (who initially have read permissions) on a SharePoint site, can add themselves to a group which has contribute permissions to a document library. This is something similar to what Moodle can do, where users can enrol themselves on a course.
My thinking is that I'd setup a list that allows all users to have contribute permissions. A user would then add a very basic list item which would start a workflow. The workflow would add the said user to a group that already has contribute permissions to a document library.
If it helps, here's the reason:
We have a lot of students accessing our SharePoint site (well over 2000), and all students are under a general AD group. To use the SharePoint Learning Kit (and therefore make use of SCORM content), there has to be a SharePoint group with specific rights, and that group should, ideally, contain individual users rather than AD groups (depending on the size of the AD group). Unfortunately, there isn't a way to get our learner record system to expose a field which SharePoint could 'see' which is why all students are under a general AD group. Because there are so many students (some with similar names), it would be a hard task to get lecturers to filter through each student to add them manually to the SLK group that's needed. Which is where this idea comes in. A student could enrol themselves into the SLK group and get access to the SLK material.
And breathe.
There are a lot of possible ways to do this. For example you can create custom timer job which will run every 15 minutes and synchronize sharepoint group with list you mentioned. If you want to stick to workflow way you can create custom workflow action which will add user to sharepoint group and then create workflow which uses this activity using sharepoint designer.