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?
Related
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.
Our contact page includes a NetSuite Case form which allows us to direct workflows to the proper department within our company (i.e. warranty, sales, etc.). However, NetSuite does not create contacts with this information, opting instead to keep them all in "Anonymous Customer". However this makes things difficult if we need to bring the person into the system as a new customer or potential lead.
Is there any way to convert info submitted by a user online via a case form into a contact?
NetSuite creates a new anonymous customer if the company submitted in the case form doesn't exist or if the company is not submitted. If you have the Company Name field added to your form and the form is submitted with an existing Company name, a new contact is created for that company. You can also pass the company name by parameter in the url using &companyname=mycompany and a new contact will be created in that company with the information submitted in the case form.
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.
I was recently tasked with taking over the SharePoint administration for my company, but I have very limited SharePoint experience. I'm using SharePoint 2010.
I have a List with a few built-in columns (like Status, Assigned To, etc) and I'd like to perform a few actions when a new List item is created: change the Status and Assigned To columns of the List item, send out an email, and then create a task for the user's manager to approve it. However, in SharePoint Designer, I cannot figure out how to create a Reusable Approval Workflow and associate it to a List, or a List Workflow and add an Approval Task to it.
If I create a Reusable Approval Workflow, when I try to use the "Set Field in Current Item" Action, I don't have any of the List Columns available (to set the Status, Assigned To, etc).
And when I create a List Workflow, I can access the columns for the list (Status, Assigned To, etc) but I can't figure out how to make the new List item go through the Approval process.
So my question is: how do I Associate a Workflow to a List, change some of the List column properties, and create an Approval Task for the Manager when a new item is created?
Am I missing something here or am I not approaching this correctly?
The easy way is just opening your site with designer and configure the approval workflow from there. You can select the list and make all the changes. I would give you a step by step guide, but some did this awesome article, so check it out http://plexhosted.com/billing/knowledgebase/226/How-to-create-a-simple-approval-workflow-in-SharePoint-Designer.html
I discovered the answer to this question on my own. It's due to the way SharePoint handles Tasks during a workflow. I was using the "Assign a Task" or "Assign a To-Do" when I needed to use COLLECT DATA FROM USER. This will return the Id of the task, which can be used later to retrieve the user's Approval or Rejection.
Did you end up creating a custom workflow to do all tasks yourself?
I have also tried a List WorkFlow and a Reusable Workflow and started by copying the "Approval - SharePoint 2010" workflow as a model in both cases. The caveat then is the users are tied to completing both the task and workflow items that are created.
An approver wants to receive the email to Approve or Reject a request on a Calendar from the Approve/Reject View in SharePoint and let that be it. They do not want to track tasks on Approval.
A requestor only wants to receive an email that their request was Approved or Rejected and enter another for a different time if the initial request was rejected.