Skip to main content

Async Plugins vs. Power Automate Flows

SharePoint 2010: Bug in Advanced Search Webpart

Today I found a nasty bug with the AdvancedSearchWebpart:

I put the wepart on a standard web part page:

Then I went into edit mode and deselected the other search text box fields so that I only have the first one "All of these words":

Then I entered a search string "test" to see what's happening:


The result was this:


I turned on the debugger to find the place where the error appeared:

It crashed in the method "ComposeTextSectionQuery" because the hidden fields won't be rendered and therefore the attempt to access "elements.PhraseQueryTextBox.value" will result in the error mentioned above.

I thought this was fixed with MOSS2007 already. Is Microsoft going steps backward with SP2010?
I hope this will get fixed soon!


Comments

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...

Async Plugins vs. Power Automate Flows

Choosing Your Automation Tool Choosing the right tool for automation and business logic in the Power Platform and Dynamics 365 is crucial for building scalable, maintainable, and performant solutions. Both asynchronous plugins and Power Automate flows can execute logic in the background, but they are designed for different scenarios and user profiles. This interactive guide provides a comparative overview to help you determine the most suitable option for your specific requirements. At-a-Glance Comparison This chart provides a visual summary of the relative strengths of each tool across key decision factors. Hover over the points for more details. Interactive Criterion Explorer Sel...

CRM 2013: Translation import error: The value passed for ConditionOperator.In is empty

This week a very evil error drove me nuts. In CRM 2013 I tried to import a translation file into an organization. It always ended up with this error message: The value passed for ConditionOperator.In is empty I was like what in the world does this message mean. If an old school approach in splitting up the file into serveral smaller Import files I finally figured out that the following lines in the "Localized Labels" sheet caused this trouble: RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.ToolTip.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.ToolTip.LocLabel To resolve t...