These days I’ve been using the new Caml Query Builder – CamlDesigner that is around the block and in my opinion seems very competent and speeds up the sharepoint delevopment.

For everyone who knows… the CAML when gets bigger and complicated, it is a pain in the ass!

So, for the presentation, the tools is developed in WPF and the SharePoint Login is pretty cool and what is that thing for SharePoint 15?? Sounds promising…

Ok, ok the entrance was cool, but what about the rest? It does what it promises? The answer is YES. Look at the Ribbon and that Office feeling?

And…the cool catchy things about it are:

1. UI Support for ViewFields
2. UI Support for Where, OrderBy and QueryOptions (ok this is last one is the most cool cause I never remember all the things needed, but above all if you have complicated “or” and “and” statements, it is more easier to understand)
3. Code snipping for WebServices/REST, Object Model and Client Object Model – Great accelerators!

Very helpful tool, still with some minor bugs like expanding/collapsing windows problem but promising to have continuous updates so hopefully one day to be integrated in Visual Studio.

Congrats Andy Van Steenbergen on this one!

Well complementing this post about the Visual Studio SharePoint error:

Error occurred in deployment step ‘Activate Features’: Unable to locate the workflow’s association data. To restore the association data to the workflow, restart the workflow settings wizard by selecting the workflow node in Solution Explorer and then clicking the ellipsis button (…) on one of the properties in the Properties window that has an ellipsis button.

I’ve found another solution to the problem by selecting the workflow SPI in the Solution Explorer, then in the Properties pane, set Auto Associate to False fixes the issue.

So you been working aroung BCS, and tried every step on tutorials (good ones, like these)… but in the end, data is not presented to you and you receive error on the items display.

Ok, you have to increase your throttle maximum… how? Here it is:

$bdcProxy = Get-SPServiceApplicationProxy | where{$_.GetType().FullName -eq(‘Microsoft.SharePoint.BusinessData.SharedService.’ + ‘BdcServiceApplicationProxy’)}

Once you have a handle on the proxy, you can start working with the throttling rules. BCS throttle management works on a change-and-refresh strategy. If you do anything to change a throttling rule, you should re-fetch it from BCS to be sure that you have the latest copy. To view a rule, run a command like this one:

$dbRule = Get-SPBusinessDataCatalogThrottleConfig -Scope Database-ThrottleType Items -ServiceApplicationProxy $bdcProxy

Type $dbRule by itself, you’ll see something like this:

Scope: Database
ThrottleType: Items
Enforced: True
Default : 2000
Max: 1000000

Scope and ThrottleType describe the rule you’re working with. Enforced represents whether it’s turned on, and Default is the limit that is applied to external list. Custom web parts can override the Default limit and work on more data than external lists; they are instead limited by the Max limit.

Once you have a rule, you can change it using a command like any of these examples:

# This increases the limit for external lists to 3000.
Set-SPBusinessDataCatalogThrottleConfig -Identity $dbRule -Maximum 1000000 -Default 3000

#This disables a throttling rule. Notice the “:” instead of a space.
Set-SPBusinessDataCatalogThrottleConfig -Identity $dbRule -Enforced:$false

#This enables a throttling rule.
Set-SPBusinessDataCatalogThrottleConfig -Identity $dbRule -Enforced:$true

Your update is immediatly commited by Set-SPBusinessDataCatalogThrottleConfig, but it may take a while to appear on the external lists.

A oldie this one but always useful.

When you create a webpart page on SharePoint 2010 or 2007 for that matter, the quick launch disappears… (oh bummer).

With SharePoint 2007 all you needed to do was edit the page in SharePoint Designer and remove the following 2 lines:

< asp:Content ContentPlaceHolderId=”PlaceHolderNavSpacer” runat=”server”></asp:Content>
< asp:Content ContentPlaceHolderId=”PlaceHolderLeftNavBar” runat=”server”></asp:Content>

With SharePoint 2010 you also need to delete the following:

< style type=”text/css”>
body #s4-leftpanel {
display:none;
}
.s4-ca
{
margin-left:0px;
}
</style>

The quick launch will now display on the web part page.

I’ve made a simple InfoPath form, and in “Submit Options”, checked  “Perform custom action using Code”, and write some custom code…

Then i run the debug over this code. The InfoPath formular opened in preview mode, and i could successfully step through InternalStartup method.

I did put some data in fields and clicked on “Submit” button. I expected to be continue debugging at the beging of “FormEvents_Sumbit” method, but i got this error message:

“System.Security.SecurityException
Request for the permission of type ‘Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ failed.
at TEST_FORM2.FormCode.FormEvents_Submit(Object sender, SubmitEventArgs e)
at Microsoft.Office.InfoPath.Internal.FormEventsHost.OnSubmit(DocReturnEvent pEvent)
at Microsoft.Office.Interop.InfoPath.SemiTrust._XDocumentEventSink2_SinkHelper.OnSubmitRequest(DocReturnEvent pEvent)”

______________________________

Resolution

- Open your form in Info Path Designer and open the FormOptions.

- Click on the “Security and Trust” hyperlink.

- Uncheck “Automatically determine security level”

- Check Full Trust (the form has access to files and settings on the computer)

- Publish your form

…and then test if the problem still occurs.