This is a question about Sharepoint Online. I have a form collecting information which, with the help of Power Automate, is pushed to a Sharepoint list and we have a number of different users accessing it who are meant to be editing different fields. I would like to achieve the following:
some fields of the list should be read-only (I believe this can be done in PowerShell);
different users should have access to different fields, but some fields should be read-only for one user and editable for others.
So if the list has fields A, B, C and D and we have users Paul and Mary:
A should be read-only for both of them;
B and C should be visible but read-only to Paul and visible but editable to Mary;
D should be hidden from Paul, but visible and editable (or read-only) to Mary.
Is there anyway to achieve this? Essentially, we are after something like views but restricted to a user subset with editing restrictions and them not been able to click anywhere to get the full item.
Regards,
George
I might be wrong but you can grant such privileges only if you are the owner. I made almost the same thing before by going to the person responsible for department site and made myself an owner, then I specified which users can edit or not
No. As per my knowledge, in SharePoint Online, there is no OOB way to set specific view-level permission.
Related
I have a ModelForm which asks for his dreams from the users. But I want users to provide with the "Add More" button so that they can submit the form (form fields) all at once without being the headache of reloading the page everytime the user presses ADD More
For example, If a user is done with telling its one wish, he/she can n number of more wishes and once he/she presses Submit , the form should then submit the answer to the DB.
How can I make a model for this? Will a single
class Wish(model.Model):
user=models.Foreignkey(User, on_delete=models.CASCADE)
wishes= models.Charfield(max_length=1024)
and a form from this model to render the form????
A user can have any number of wishes available in the DB so that he/she can delete at any point of time by checking/unchecking.
Your model seems mostly ok as far as I can tell from your (very vague) specs - I'd just possibly add a timestamp (creation date) to it.
For the "add more" feature, that's (part of) what formsets are (with a bit of js).
EDIT:
is the ForeignKey suitable or some other relation? because A user can have many wishes. So how do I connect all of them? I mean two users might say the same wish so there will be n copies of that wish. Good method?
Well, depends on your specs, really. If wishes are "private" to a user (no other user can see them), your design is fine that way - you may have more or less similar wishes indeed, but chances are each user will formulate it slightly differently so you'd need some natural language analysis to spot those "near duplicates".
Now if existing wishes are visible by all users and they can either choose from existing one or create their own, you'll probably need two relationships: a one to many (foreign key) for the "author", and a many to many for users that selected it (including the "author" so you can easily do stats on how many users have the same wishes).
I am using DataGrid for displaying table. One of the columns in Datagrid consists of XamFormulaEditor. Also, there are some custom variables that are assigned to XamCalculationManager's Named references so that they are visible to user when he types formula in XamFormulaEditor. I have couple of problems with ContextualHelp:
For Eg. if the custom variable name is "a", then in ContextualHelp list it looks like [//a]. Isnt't there any settings to make it look like [a] ?
Is there any way to filter the contextual help to not display standard functions and only display variables that we want ?
After looking into this and doing some research, ContextualHelp on Infragistics XamFormulaEditor for custom variables has been determined to be a new product idea. You can suggest new product ideas for future versions (or vote for existing ones) at Infragistics new site for features:
http://ideas.infragistics.com.
There are many benefits to submitting an product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Maybe this isn't the correct place to ask, but I asked this question on Joomla forums and did not get any answers. If someone can help me or at least point me in the right direction, I would really appreciate.
My question is: In a Joomla 2.5 website, I want to create two different kinds of forms for registering users. Maybe "registering" isn't the correct term. I want to create something like a very simple database which will hold records for two kinds of users:
- one which will be interested in working in projects, so in this case the form will have more fields and specific details to fill
- one which will be interested only in receiving newsletters from the site, and in this case only basic contact information will be required.
I did some research and found an extension named AcyMailing which can handle the newsletters for example, but I need to have all my potential users registered as Joomla users. I would like to avoid that if possible. If not, how can I differentiate the two kinds of users on registration, so the visitor can choose which option he wants and in this case, add more information to the registering process, if possible.
I'm not very experienced with Joomla, but since the site in question is already implemented using it, I don't have much choice.
Thanks in advance!
Chronoforms. Most definitely here would be a great use for their AWESOME free component. Your forms can work as registration forms (should you desire that); or can also just be free standing forms that log the information filled out on them to your database which you can later use however you would like (i.e. compiling a mailing list or something of that sort).
The form wizard makes it almost bullet proof, then you can have a form for 1 type of user to fill out, and a form for a different user build different ways.
That will get you the data - in order to mass mail those people you'll need a way to extract their emails out of the database (or find an email component that will let you email based on certain fields in the database or what have you); but it's totally possible and would be easily done I think with 1 simple mySQL query on your database table created by chronoforms.
In terms of something that will solve your issue quickly and get you the info you're looking for in two separate ways - chronoforms will do that exactly.
I'm building a database that needs to display tables as lists and allow the user to export such lists as Excel spreadsheets.
Creating the reports, showing them as lists and providing the button for exporting as Excel was not a problem, however I noticed that when I show those lists the user can still edit them, hence add/deleting records and modify the content of existing records.
I'd like to find a way to avoid such modifications when visualizing the list, in such a way to be sure the user does not accidentally change data.
Any idea as to how to do this? I'm using Filemaker pro 11
Thanks in advance.
There are a couple of different ways that might be appropriate, depending on your needs:
In layout mode, click on the field, go to the Data tab of the Inspector, and turn off field entry in 'Browse' mode. (You also have the option to turn off field entry in 'Find' mode. And you can select multiple fields at once to make the selection for all of them.) This is appropriate if your users can regularly enter data into these fields but you don't want them to enter data for this particular layout.
In Manage Database, under the field options, turn on Prohibit modification of value during data entry in the Auto-Enter tab. This is appropriate if you will only be changing the value of a field during an import or with a script.
In Manage Security, create a new Privilege Set that is View-Only for that table (or for those fields). This is appropriate when some users should be able to modify the data and other users should not be able to modify the data.
There are other methods, as well, but those are the three most common for limiting user access to data.
Hi everyone I have a few questions about the django admin.
First the relevant details. I currently have Client, Printer, Cartridge, and Order models.
The Printer model has a ManyToManyField to the Cartridge model, which would allow you to select all the cartridges that can be used with that printer.
The Cliente has a ManyToManyField to the printers which they own.
1) I want to create an Order through the Django admin which lets your specify the Client, a dicount, and multiple cartridges through a ManyToManyField. This is getting kinda tricky because I have to do it through another table that specifies whether it's a new Cartridge or a refill.
2) I want the admin to filters the Cartridges to only show the ones that belong to the printers that they own.
3) Also I would like to have a field that holds the total price of their order, but it should calculate it based on how many cartridges they have added to the order. I don't know if this should be done by adding more of the same cartridge to the order or by having another field in the related table that specifies the quantity.
Can this be done in the admin or do I need to use a form? And if so how would I go about adding this to the admin? It seems difficult and probably something I will have to do in multiple parts since in order to filter the list of cartridges I have to know the client beforehand.
As far as I can see, no, it's not really possible. The development version has some methods for limiting foreign keys, but it doesn't seem to me that limiting based on the customer is possible, since it depends on separate foreign keys.
The best suggestion, if you're really bent on doing it in the admin form, would be to use Javascript to do it. You would still have to make AJAX calls to get lists of what printers customers had and what cartridges to show based on that, but it could be done. You would just specify the JS files to load with the Media class.
But I think that's more work than it's worth. The easiest way I would see to do it would be with Form Wizards. That way, you'd have a step to select the customer so on the next step you know what cartridges to show.
Hope that helps!
I've worked similar problems, and have come to the conclusion that in many cases like this, it's really better to write your own administration interface using forms than it is to try and shoehorn functionality into the admin which is not intended to be there.
As far as 3) goes, it depends on what your product base looks like. If you're likely to have customers ordering 50 identical widgets, you probably do want a quantity field. If customers are more likely to be ordering 2 widgets, one in red, one in blue, add each item separately to the manytomany field and group them in your order interface.