Tag Info

Hot answers tagged

2

To fetch ID from Lookup field, you can use following code: SPFieldLookupValue fieldLookupValue = new SPFieldLookupValue(item["emp"].ToString()); int lookupID = fieldLookupValue.LookupId;


2

You can do so using jQuery as there is no mechanism in the left navigation to allow you to embed that. So after referencing jQuery in your master page, give your left navigation link a url of / just as an initial value, then give it a unique description, for example give it a Description of: Feedback Dialog, that will give your link a title property of ...


2

Select the option for "Return field as" to Lookup Value, while selecting [%Current Item:Application%] For reference, have a look at screenshot below.Instead of "As String", select Lookup Values,Comma Delimited


1

Does it continue, using the updated date? Depending on your workflow, it could cancel altogether, but usually it will use the new updated value. Does it continue, using the old date? See above. Assuming either of the previous is true, is a new workflow spawned upon change? Depending on your workflow this can happen, but most users only trigger workflows ...


1

I have faced almost same issue due to list threshold limit when my items exceeded the limit to 50K while limit was only 5K (as by default). You have two options here. Disable throttling for the library. Create an indexed column and then use that column in your custom view as a filtering column. Creating index column may take some time based on data ...


1

Appear to have got to the bottom of this. The compiling was going round in circles due to McAfee AV blocking access to C:\Windows\Microsoft.NET\Framework64\v2.0.50727. Digging deeper this inherited environment didn't have the best practice AV exclusions published by Microsoft applied. Once the exclusions were added, the issue went away. Still intrigued why ...


1

Please, ensure, that the IIS application pools that belong to these SharePoint web applications are up and running. If they are running, you can try to restart them. Often it happens as you install a new solution into the SharePoint farm. Most of the time this issue is only temporary (1-2 Minutues), but can be quite frustrating. See this post as reference. ...



Only top voted, non community-wiki answers of a minimum length are eligible