Unable to understand why does Update Panel does do the soft post back (partial post back).
Nothing happens on page after the dropdownlist selected Index change.
tried to ref :http://msdn.microsoft.com/en-us/library/ff650218.aspx
Would be thankful if any already cracked up the isse for SharePoint 2013.
request is processed on dropdown change without any exception but does not reflects UI
you should check your trigger, perhaps you dont have it, or its not referencing the control properly
take a look here, and if you need, make a post over there
https://sharepoint.stackexchange.com/questions/110432/sharepoint-2013-webpart-timer-not-tick/110436#110436
Related
I have a basic knockoutjs project loading data from a SharePoint 2013 list scenario. Getting data and displaying data is easy, the problem that I'm running into is on the edit mode displaying the proper control. Everything should not be a textbox. This means the people picker control to dropdownmenus to calendar controls.
MSFT has some pretty good documentation on using the client side people picker control here"http://msdn.microsoft.com/en-us/library/office/jj713593.aspx
The problem that I have is calling this control inside my viewmodel.
Setting the value of the control doesn't look difficult courtesy of this blog post: http://www.sharepointcolumn.com/sp2013-setting-people-picker-value-in-newform-aspx/
I attempted to looking into computed values, but that doesn't seem to work. Does anyone have a blog post that I skipped over? The closest related post that I can find: http://yetanothersharepointblog.wordpress.com/2012/12/11/working-with-sharepoint-lookup-columns-in-knockout-js/
Lastly since it seems that I'm the only one doing this, does anyone think that I should not be reinventing the wheel with my forms and should just link each item to the appropriate SharePoint list item in edit or display view? I suppose that would be easier.
From a SharePoint Professional to another, I would highly recommend you to do that.
Just redirect the user to the item edit/display item page an let SharePoint take the leash of how to handle UI form elements.
Because, assume that you implement your custom form, what if the user decides to add one more site column to the list? Will you update your code to support another field?
From my personal experience with the beast I've come to the conclusion that structural implementation over already existent functionality tends to go wrong.
Also, if you have some kind of listing of items custom made and you want to provide editing, try to do something opening a pretty SP.UI.ModalDialog, its elegant and you use the sharepoint to do the work for you.
But it's just an advise.
I'm having a problem with the Person Picker control in InfoPath 2010. I enter a name and it is resolved and displayed on the control. So far, so good. Now I'm trying to retrieve the value of AccountId provided by the control. It works when I preview the form locally but when I publish it to SharePoint (this is a browser-enabled form) the AccountId is coming back as blank.
Below is the XPath I'm using. (I tried adding an index, as in "Person[1]", but InfoPath didn't like that either. Besides, I've limited the control so that only 1 user can be entered.)
/my:myFields/my:ApproverGroup/my:Analyst/pc:Person/pc:AccountId
Same result if I try to get DisplayName or AccountType--works in preview but not when I publish. And I'm publishing to my local SharePoint Server (same machine I'm developing on).
Any ideas? Thanks in advance.
I figured it out. Turns out a postback is required before the data source will reflect the value entered in the People Picker control. Why this is I don't know, but it somehow primes the control to work properly. This postback can be done once on form load and then the People Picker will work after that. So my next problem was looking for a way to force a postback on form load. Also, the People Picker inexplicably does not include a "Postback settings" property as, say, a textbox does. I resorted to enabling the postback setting to "Always" on the first textbox on my form, hoping the user will enter a value there before scrolling down to the People Picker control. It's a terrible hack, but the only workaround I have so far. If anyone can provide a better answer here please do so.
When you click on the name of a library, go to the documents tab, click on "upload document".
An upload form appears that is created using the dialog framework. The 1st choice on the form is content type.
I need to instead launch a custom infopath form that will allow me to dynamically populate a 2nd dropdown box on the page after the content type (still 1st) dropdown is populated.
I feel like I'm really grasping at straws here. At this point I could use a reference to a relevant section of a book, a link to a relevant post or even just the correct terms to put into a google search. What is the correct name for that form?
I found this which seems to teach you how to insert a customized aspx form: http://microsoftsharepointandbeyond.blogspot.com/2009/10/customizing-ootb-sharepoint-forms.html
But I'd really like one that uses Infopath instead.
Any advice or direction you can provide would be greatly appreciated.
I'm pretty sure doing this with infopath is not possible, the forms are bound to a (codebehind) class in the SharePoint object model, which handles the actual upload (add to list, set field values etc. etc.).
A custom aspx page would be possible though, exactly as the post you mentioned descibes. I agree with the post's author that an HttpModule would be best, because:
editing the OOTB upload.aspx in the 14 hive would make your environment unsupported (i.e. if anything brakes, MS will have you revert your farm to a supported state before they come and help you.
The next time you install an update for sharepoint, your changes could be overwritten.
In Sharepoint 2007, when linking to a folder or file in a Document Library, the url is long and cumbersome. Is it possible to link by the ID field?
e.g., http://domain/path/doclib/Forms/AllItems.aspx?ID=275
Whats the problem with http://domain/sites/whatever/Lists/Announcements/DispForm.aspx?ID=1&Source=http%3A%2F%2Fmoss2007dev%3A20000%2Fsites%2Farcnet%2FLists%2FAnnouncements%2FAllItems.aspx
If you remove the Source parameter your left with Whats the problem with http://domain/sites/whatever/Lists/Announcements/DispForm.aspx?ID=1. The only problem you'll have then is that the cancel button will not necessarly return you where you came from. (The cancel button would send you back to the default view as far as I know..)
On the other hand you could sneak in some code which does the redirect from a view or actually opens the document.
I know you asked specifically about 2007, but SharePoint 2010 has a cool new Document ID feature that will allow you to refer to any document in the Site Collection using the following format:
http://[sitecollectionurl]/_layouts/DocIdRedir.aspx?ID=[documentID]
Here's the deal, I have various event receivers registered to a document library:
ItemAdded
ItemAdding
ItemFileMoved
ItemUpdating
These event receivers work as expected in all cases, APART FROM copying and pasting into explorer view. It's worth noting that the event receivers do fire off when MOVING from explorer view into explorer view!
Has anyone else experienced this? Is there a way to fix this?
Workaround:
Create a SharePoint Designer Workflow, attach it to your Doc Library.
Make it run when the item is changed or updated
Give it a simple step with the following Action (no conditions)
Update field in the Current Item
Select the "Title" field, set it to "Changed".
You are probably able to capture the events from your .NET logic now.
The problem you are encountering is one of the most annoying features of SharePoint, for some reason it not only overlooks our metadata requirements but also the events you are trying to capture when using the explorer view or unc path. I beleive the only workaround for this is to create a WWF workflow.
If you are thinking of keeping the drag and drop functionality, and losing the Explorer view, you might want to look at this..