But this method doesn’t work for External Lists.

Fields in an external list don’t have an SPFieldType, they have various field types according to your BCS connection. For example: you can have a field from type “Decimal” when you are working with an External list connected to SQL Server Table.

In this case you can check the field type using SPFiels.TypeAsString method. This method will return a type as a string so you will get something like “Number” or “Decimal” as a result. It works for both External and regular SharePoint lists.

If you still have an error when you try to execute a query try to set your RowLimit to 100 or 200. I found out that in some cases if there are too many results for the query FAST will stop the execution with error. Try to set minimal row limit and check again.

I hope it will help somebody.

I don’t want to write here how to do it –there are many great articles about this.

If you are looking for guide like that you can use these two really great posts:

• http://sharepoint-sezai-moss-2007.blogspot.com/2011/03/creating-fast-search-managed-properties.html
  
• http://blogs.msdn.com/b/shad_phillips/archive/2010/05/31/fast-2010-for-sharepoint-2010-managed-properties.aspx
  

I just want to put your attention to one little but very confusing thing:

In Central Administration we have an option to manage and create Managed Metadata Properties for search. To access the managed properties page you need to click on FAST Search Query Service Application under the “Manage Service Applications” link. There you can manage FAST Search Query settings BUT you don’t have a direct link to the “Managed Properties” page there. To get to the page you should click on “FAST Search Administration” link (the second one) and there you will see the right “Managed Properties” link.

The “wrong” link will get you to manage standard Metadata Properties of the standard SharePoint Search and FAST Search doesn’t use these properties.

For this task we need to use another web service: getUserProfileByName.

We need to query this web service with manager AcountName to get the data. Sounds simple? It is!

Here is a step-by-step guide to help you through it:

Scenario: we have an InfoPath Form with 3 fields: Current User Name, Manager Name, Manager Phone Number. We need to populate data.

Current User Name:

1. Create a new data connection. You need to receive data about your current user.
2. Choose SOAP Web Service as a source and then type this URL into the text box:

   http://serverName/_vti_bin/UserProfileService.asmx?WSDL (change the serverName to yours).

3. Choose GetUserProfileByName method. Do nothing else but clicking “Next” until you will need to give the name to your data source. Name it getUseProfile.
4. Drag a new text box to your form. Set the default value of this text box this way:

   Enter the default value function window:

   

   Click on “Insert Field or Group” -> Choose the data connection we just created -> choose the “Value” field from the tree -> Click “Filter Data” to get the right property for our user.

    

   

   Filter settings:

   

   

   

   The result:

   

Common Manager Account Name

1. Create a new data connection. You need to receive data about your current user.
2. Choose SOAP Web Service as a source and then type this URL into the text box:

   http://serverName/_vti_bin/UserProfileService.asmx?WSDL (change the serverName to yours).

3. Choose GetCommonManager method. Do nothing else but clicking “Next” until you will need to give the name to your data source. Name it GetCommonManager.
4. Drag a new text box to your form. Set the default value of this text box like so:

   Enter the default value function window and choose the “Name” field for the GetCommonManager data source.

   

    

   That’s it!

Common Manager Phone Number

1. Add a new textbox names “Manage Phone”.
2. To fill this field automatically we need to add a rule to the “Form Load” rules to trigger the filling.
3. Delete the default value from the Manager Name field.
4. Click the “Form Load” under the Data tab on the ribbon.
5. Add a new action: Set field’s data. Set the Manager Name like we do in the previous part.
6. Click on the Manage Name text box.
7. Click “Manage Rules” on the Ribbon.
8. Add a new “Action” Rule

   

9. Add a new action: Set field’s value.
10. In the field textbox choose the AcountName field from the queryFields of the getUserProfile data source.

    

11. In the value textbox choose your manager account name field.

    

12. Save this action.
13. Add a new action: Query for data

    

     

14. Save this action.
15. Add a new action: Set field’s data.
16. Put the WorkPhone of the manager to the Manager Phone field just like we do with preferred name of the current user.

The complete rule:

The result:

]]> http://spointblog.com/2011/07/29/how-to-get-common-manager-personal-data-%e2%80%93-infopath2010/feed/ 0 http://spointblog.com/2011/07/23/how-to-get-a-featured-form-id-in-infopath-form/ http://spointblog.com/2011/07/23/how-to-get-a-featured-form-id-in-infopath-form/#comments Sat, 23 Jul 2011 12:41:05 +0000 Sveta Yerpilev http://spointblog.com/2011/07/23/how-to-get-a-featured-form-id-in-infopath-form/ The scenario is very common: You create a new form template and want to use the ID of the form as part of the form name.

But there is a catch here – the ID doesn’t exist until you will submit the form to the SharePoint library…

Here is a very simple way to calculate the feature ID of your form in the SharePoint Library.

First of all let’s create a new data connection to our SharePoint List.

Choose the ID column to receive in the last window of this wizard:

After this we can create our submit data connection.

As you can see in the Image (if not I will explain it step-by-step later) in the “File name” text box I wrote a function that builds the form file name after the submit process. For the name I’m using a constant “Form ID-” and the function that returns the next item ID in the list. As you can understand we have a little issue here if someone will create another form in the second that between the retrieving of ID and the actually submitted one but I think the risk is very minimal…

So, how do we retrieve the last ID number from our form library?

To do this we will use the “max” function of InfoPath. Insert the “max” function to the formula text box. You will see something like this: max(double click to insert field)

Click on the “double click to insert field” link and in the “Select a Field or Group” window choose the data connection to your form library. You must see the connection tree and under the “dataFields” you will find the ID field. Select it and press “OK”.

That’s all, our function for the form “File name” is ready to use. Save all settings and don’t forget to connect this submit data connection to some button in the form.

Good Luck!

So I checked out the original Slideshow page that comes out of the box with Picture library.

And it was pretty nice, I have to say. And guess what? You can actually change the slideshow that appears when you click the “This week in pictures” slideshow button!

Here are a couple of tips how to improve the default slideshow and redesign this page:

1. First step is to open the Slideshow.aspx using SharePoint Designer. You can find this page
under you picture library folder->Forms

2. Do you want to start playing the slideshow on start? Add this code before the “body” closing
tag:

<script type="text/javascript">
StartSlideShow();
</script>

3. Want to hide controls? Add this code before the “head” closing tag:

<style type="text/css">
.ms-formdescription {
display:none;
}
</style>

4. Want to add the slideshow to a regular SharePoint page? Open your page. Add the picture library
web part to the page and hide it. Add “Content Editor” web part to the page under your picture
library and there add this code:


<script type="text/javascript">
if (IsImgLibJssLoaded()) SlideShowContent();
</script>

Below are all the tricks together prepared for copy-paste to Content Editor (this works for SharePoint 2007/2010):

<style type="text/css">
.ms-formdescription {
display: none;
}
</style>
<script type="text/javascript">

if (IsImgLibJssLoaded()) SlideShowContent();

StartSlideShow();

</script>

Enjoy!

Theoretically it can be changed manually but the maintaining of the manually manifest is too hard.

So after a couple of experiments I figured it out.

Here is my solution to change web parts namespace and stay alive:

1. Change the namespace in following files:

• VisualWebPart.cs
• VisualWebPart.webpart
• VisualWebPartUserControl.ascx.cs
• VisualWebPartUserControl.ascx.designer.cs
• SharePointProjectItem.spdata (If you don’t see this file click the “Show All Files” button in the Solution Explorer toolbar)

1. Click the Right-Mouse-Button on the Project Name and select “Package”.
2. After the package will be created successfully check out the manifest.xml under the pkg->Debug/Release->[ProjectName] folder (If you don’t see this file click “Show All Files” button in the Solution Explorer toolbar). Just check that safe controls were updated.
3. Reopen your solution. The Package Designer is now up to date.

The language of this installation package is not supported by your system.

 

It was an English 64bit version of SPD and my server definitely uses English as its system language…

Hmmm…Very Strange…. Let’s check our “Microsoft Office 2010 Language Preferences“.

Bingo!

Here my default editing language is not English.

After I changed this configuration and set English as my default editing language this error was gone.

The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly.

But in the strange way all users that was set as Site Collection Administrators run this workflow without any problem. Strange, the issue is definitely not in the outgoing e-mail settings…

After I tried to give end users every possible permission level (even Full Control) without any luck I finally checked the settings of the SharePoint group that I’m trying to send e-mail to. I saw that the “Who can view the membership of this group” is set to “Group Members”. That’s It! In this case any other user can’t see who is the member of the group so he can’t send they an e-mail. And because the workflow always run with the end user permissions the e-mail cannot be sent via workflow.

So after I changed the configuration and checked the “Everyone” option for “Who can view the membership of this group” my issue is gone.

http://martinbruce.blogspot.com/2011/05/sharepoint-2010-multiple-domains-people.html?showComment=1307607931974#c2148053790141003310

These two lines did the work for me:

stsadm -o setapppassword -password "password"
stsadm -o setproperty -pn peoplepicker-searchadforests -pv "domain:domain\user,password" -url "web_app_url"