I've encountered a very weird behavior when editing any field on an Item(new or old) in a custom list where this specific dropdown field's text value changes from "Temporary" to "Permanent".
As a background we've added this field a year ago and just moved the position of this field by manually cutting and pasting on the first portion of the NewForm and EditForm.
I've already checked that there are no workflows that automatically start when an item is edited because they are configured to be manually started.
Could this be a content type issue? Not sure why it automatically changes value as soon as I press save in the Edit Form. I would like to experiment in deleting the portion below from the EditForm, but i'm concerned if I delete this in the EditForm will I lose any data?
Admittedly, I don't have much knowledge about SP :(
Try to check is any event receiver attached to the list.
$spWeb = Get-SPWeb Identity http://Site
$spList = $spWeb.Lists["Custom List"]
$spList.EventReceivers | Select Name, Assembly, Type
Related
When I create a list, I have gotten into the habit of doing the following:
Change Title field name to Item
Give it the default value of View
Go to Advanced Settings
Allow management of content types > Yes
Click Save
Then in Settings, click on the Item type
Then click on the Item field and select Hidden
Then go back to Advanced Settings
Allow management of content types > No
Click Save
The result of this is that:
The Title field (now called Item) is hidden in the form
I have a column called Item, which has the link View in each row (which opens up the item)
I can’t remember why I started doing this (possibly one of the reasons outlined in this video), but the use case must have demanded it and I just kept doing it.
However, lately I have been having troubling thoughts about whether it negatively effects indexing or has any other undesired outcomes.
For example, I did a search in a list the other today, and in the drop down search results that were displayed, I just got multiple rows of the value View.
I also read just before posting this question that list items in the recycle bin will be identified by the value that was in the Title column. So if they all say View it will be impossible to differentiate one from the other.
So I just thought I would see if there is any authoritative, definitive best practice around the Title column, and ask if my convention is bad and if so what I should replace it with.
Thank You.
(Edit: I also hide the Title column in document libraries, as it doesn’t seem to serve a purpose, as clicking on the value in the Name column opens up the document anyway - therefore the ‘link’ action of the Title field is not required).
I'm new to Power Apps, I'm facing this issue.
enter image description here
This is a PA form when I select Projects value in Time entry field the below two fields are enabled Project and Project Role but when I change to other option like this
enter image description here
Project and Project role are hidden for other option selected except Projects option in time entry field.
Everything is working fine but problem is coming when I edit any existing records of list and try to change the Time Entry field option when I'm changing the option from Projects to other options the below two fields disabled automatically which is fine but when I save this form after making changes the value of Project and Project Role remains in list which was existed for Projects option before editing.
So what I need here when I edit the existing records so value of Project and Project Role also wipe from SharePoint list when I select options other than project in time entry field.
Thanks in advance.
Forms on PowerApps are defined by cards. Cards have two important properties.
Default, which is the value you pass into the fields and show to the user. Usually this is just the value of the source
Update, which is the value you write back to the source. Usually, this is just the value of the field
You can do a lot by modifying default and update, which allow you to do all sorts of checks and logic on how different data should be transformed.
In your case, set the update value for project and project role to this
If(Self.DisplayMode = DisplayMode.Disabled, Blank(), dropdownvaluehere)
Whenever that card is disabled, it will write nulls to the list, regardless of what the dropdown says. Whenever the card is enabled, it will refer to the dropdownvalue.
As an aside, Consider using a dropdown box instead of a combobox if not necessary, as comboboxes have nice features like letting you select more than one value at a time, but tend to be more temperamental and break and forget values.
I have a button for the user to submit a SharePoint list item for review. On the click even a variable is set which updates the text status field in the SharePoint list. Here's how the status field is updated, it checks if the value is blank and sets it to draft status, if that fails then it checks the variable status update field for blanks, if nothing in the variable then it uses what is stored, otherwise it takes the value from the variable:
If(IsBlank(Parent.Default),"Draft",If(IsBlank(varStatusUpdate), Parent.Default,Text(varStatusUpdate)))
For the date field, I'm also checking for nothing on the SharePoint list, then I'm checking the same status update variable. When blank, use what is stored in the list. If the value is "pending approval" then it should get current date.
If(IsBlank(Parent.Default),Blank(),If(IsBlank(varStatusUpdate), Parent.Default, If(varStatusUpdate="Pending Approval", Now(),Parent.Default)))
When testing the updated Now() value appears on the screen but it isn't saved to the list. When published to SharePoint the value is never saved or updated.
Any ideas?
One way of updating the logic and the value from a Datacard in your form to a datasource is to change the Update property for a specific Datacard
Example -
Originally:
Changing the Update values:
or
Where DataCardValue2_6.Text is the text input for the column.
Only way I could get this to work was to use the patch command like below:
Patch('LTRequest', ThisItem,{
SubmitDate: Now(),Status:Text("Pending Approval")});
Back();
I have a custom SharePoint 2013 list (which started as a SP2010 list) with roughly 2,000 items. It was recently brought to my attention that I am having a strange issue with a check box/boolean type. I can't recall if it was originally created as a Yes/No column in SharePoint before the web form was created in InfoPath.
The field name is Report Received. Up until now, and only for troubleshooting, the checkbox was never actually on the form. I had a rule where if a question was answered, the field value was set to 'true' in lowercase without quotes.
If I create new item in the list, the checkbox works as expected.
If I attempt to edit a previous item that the value was already false, I get a validation error upon save, that states that only 'true' or 'false' is allowed.
In conclusion, I can only assume that for a period of time, something was buggy in my rule/form/field.
My goal is to either set that field to blank on the items, or fix the assumed corruption in the field on those items.
Fortunately, I don't have many items to fix.
One idea i had was to create a view called "Test".
On that view i dragged the Report Received field on the form. I also added a calculated field below it which shows me the current value of the field, and 3 buttons, each with a rule, to either set the value to blank, set it to false (lowercase), set it to true (lowercase).
I then opened an old item that is giving me the error, to test my new buttons.
My first observation is that the calculated field indicates that the value is currently false (lowercase)
Unfortunately, when i click any of them, i instantly see that the checkbox turns red, indicating that only 'true' or 'false' is allowed when i mouse over the checkbox.
The strange thing is that my calculated field indicates that the value changed to TRUE in uppercase, even though the box is unchecked.
I am noticing this before attempting to save the form.
If I create a new item in this list, and go to my "test' view, the buttons work just fine.
While InfoPath seems to prefer true and false, the value in the SharePoint lists are Yes and No.
Any ideas how I may be able remove the corruption on these older list items, without deleting and recreating them?
I am currently using InfpoPath 2010 to edit the form.
Thanks!
I am kicking myself. I ran Rule Inspector and saw that a rule i was not aware of was causing my issues. I deleted it, and now everything is working as expected.
Thanks for the info. I was experiencing the same thing and was able to find my error as well by using Rule Inspector. More specifically, my issue was being caused by a rule running on the "submit" buttons that set the checkbox or boolean field to "Yes" to match what was in SharePoint. I found that you have to actually use the formula (fx) field in InfoPath and enter boolean("true") as the formula to get InfoPath to pass the value correctly to SharePoint!
i have a sharepoint list
with 2 users for examole (user A and user B)
i need a calculated field in the list items such that if user "A" created the item the field vaule will be "X" and if user "B" created the item fields value would be "Y"
but i couldnt use [created by] in the furmiula of the calculated field !! why is that ?!! and is there another way to do what i need to do ?!
If using Sharepoint Designer is an option you can create a workflow for that list. Set it to start when a new item is created -or- edited, use a condition of "If Created_By equals ..." and an action of "Set yourfield to yourvalue", then add an Else If branch and repeat. This will always override anything a user enters in "yourfield". Takes about 2 minutes to do all of this.
I believe you can create a text field that has the default value set to [Me] which should then be usable in a calculated field.
For more complicated formulae (i.e. anything with conditional logic), try creating an event handler for the content type (or doc library). This will allow you full control to set the fields to what you desire.
The field can be hidden from the user inside the edit screens.
Make sure use the STSDev from codeplex to setup the solution for deployment.