I have a task to make a survey to be displayed in SharePoint 2007 to external users for them to fill out and submit, but not be able to view the submitted results (so they don't see what others have entered). This survey will be for outside vendors to my company to submit information about them for our records. I am open to any suggestions on how to accomplish this goal....
This can be accomplished by configuring the survey appropriately. Users will be able to see their own submissions, but not what others have entered:
Create a new Survey and populate it with your questions.
From the new survey list select Settings -> Survey Settings
Select Advanced Settings
In the Item-level Permissions section set the value of Read access and Edit access to Only their own and click OK.
Related
I have a custom people picker that fetches users from a SharePoint Group, only when the users are added manually from the Group settings.
If i add the users via SPD Workflow, the people picker is failing to read the data.
Deleted the Users and tried the Workflow, it didnt work. Removed app step from workflow and tried, still no use.
Reference to add User to SPD Group using Workflow: http://codelesssharepointinfopath.com/workflow-useful-rest-calls-add-user-to-group/
Expected: People Picker should show the users from the SPD Group
Actual: No Results found
It's probably because it's a workflow (if you're using 2010 give 2013 a try). Do you get the same issue when you use Flow? If you don't get the same issue I think you need to force a refresh via the workflow. Worst case scenario you can use REST to add the user to the group through the workflow and I would imagine that would force a refresh.
I have a number of PowerBI dashboards on our SharePoint 2013 online site. We are working on a plan to only display relevant dashboards to the user based on their user group. For example, a salesperson will only see their personal dashboard on the page. I can do this for image viewer, etc., but I cannot figure out how to edit a PowerBI webpart to target an audience. Any suggestions would be most welcomed.
KL
I suggest you to use Row level security.
Select the Modeling tab.
Select Manage Roles.
3.Select Create
4.Provide a name for the role.
5.Select the table that you want to apply a DAX rule.
6.Enter the DAX expressions. This expression should return a true or false. For example: [UserID] = userprincipalname().
And Save.
For this you need a field where the username is registered, means that user has visibility on that row. If you don't have this information, then you will need to add some information to the row, to give visibility to whom deserve it.
After you have created your role, you can test the results of the role within Power BI Desktop. To do this, select View As Roles.
And then play around to check if what you get is what you want.
Hope that helps!
I had to revert the SP page to a Classic interface, then create individual Web Parts for each dashboard on the page, limiting each Web Part by the targeted audience. The Web Parts are not visible on the main Dashboard Portal page unless you are in the targeted audience, so you could see 1 or up to 5 dashboard previews on the page. An individual page was needed for each Power BI dashboard. A user cannot be prevented from seeing the dashboard if they are provided the URL, but hiding the hyperlink and preview screenshot on the Portal page is close enough. This should be easier to execute in SP... Oh well...
Using crm when I have multiple select how can I change(edit) multiple selected records? Also is there any possibility to put permissions for different users accessing multiple edit? For example a super admin and a user will see specific fields when the edit multiple records page appear.
Bulk edit feature is OOB. To edit records in a bulk way select records you want to edit and click edit button on the toolbar. This video demonstrates that - https://www.youtube.com/watch?v=zv7C06IRV4U
To limit possibility of bulk editing open security role you want to change that privilege, open "Business Management" tab and use "Bulk Edit" privilege in "Miscellaneous Privileges" section to allow/disallow bulk editing functionality for a security role.
I've set all my security roles in CRM but unable to select the Default Tab, see screenshot below. What am i missing?.
Screenshot
Since you selected the Default Pane based on user role it doesn't create a filtered list for the Default Tab.
Call MS devs lazy or performance aware but they just cut corners there and do not query the Pane based on your user role to filter the Tab list.
I created a basic registration form using a SharePoint 2007 custom list where users complete fields on the form. I created an 'Approver' field that I'm trying to hide from customers so that only the form's approver will edit that field (approve the request - Customers tend to approve their own request). How can I hide this approval field so it can be edited by the approver only?
Attempted Solutions:
1. I set the content type for that approval column to 'hidden'. How would I access the URL to the hidden approval field so the approver can access the field and update it for that specific item? The hidden field is not visible if I click 'Edit Item'. Did I miss something with the hidden content type so that I would see the column on the edit page?
2. I customized newform.aspx in designer by removing the hidden approval field and it worked. But 'Attach File' doesn't work when the new form is customized. It spews out an errors.
Any suggestions?
Have a look at the SPListDisplaySettings component from codeplex. Adding this solution will allow you to specify how to show the fields in display, new and edit mode based on SharePoint users and groups.
May be create a custom field control (how?) that will check the current users role agains the site before choosing to display the field.
This is pretty hard core customisation compared to creating lists though.
Why not just use the Approval workflow with this list? Users would be able to create approval requests, which would automatically trigger the Approval workflow, which would create a task and send an e-mail for the approver to approve the request. Once it's approved - the status of the request would change to approved. The approver can also add a comment on the approval form, if needed.