iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

Copyright © 2025 · iT Synergy·

SharePoint – Excel Services: We can’t open the workbook in the browser because it uses the unsuported features: Grouped Slicers
SharePoint – Excel Services: We can’t open the workbook in the browser because it uses the unsuported features: Grouped Slicers avatar

By Leave a Comment

When we work with excel services making pivot tables, we have the option to create filters for our reports. As the table report can change its size because of the data, the filter sometimes move to one side to another and this is not the best thing to work with.

What I made when I faced this behaviour was open report in excel and modified the filter grouped all of them:

Then, I publised it in Share Point and when I opened the report I got the next error: We can’t open the workbook in the browser because it uses the unsuported features: Grouped Slicers. So, excel services doesnt allow as to group shapes.

However, we can use another ‘function’ to make the same behavior we were looking for when we intent to group the filters. The next figure shows the option we can choose. We have to make the same thing for each filter we want them don’t move it when the pivot table changes.

 

Cannot resolve the collation conflict between “Modern_Spanish_CI_AS” and SQL_Latin1_General_CP1_CI_AS” in the equal To operation.
Cannot resolve the collation conflict between “Modern_Spanish_CI_AS” and SQL_Latin1_General_CP1_CI_AS” in the equal To operation. avatar

By Leave a Comment

Sometimes when you are working with different database to get data the way you require, you can get the next error:

Msg 468, Level 16, State 9, Line 3: “Cannot resolve the collation conflict between “Modern_Spanish_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the equal to operation.”

It happens because the database collations of those two database I was working on have different collation as show the next two pictures:

To resolve the problem you have to identify the column which are presenting the problem. Normally you can identify them in two cases:

  • If you are working with a simple query like:

Select *

From Tabla

Where Cond1 = Cond2

The “issue” is going to be in the data you are using in the clause Where.

  • If you are working with a Merge sentence like:

MERGE PISGRSTG_Dev.dbo.Fuente AS T

USING PISGR_Dev.dbo.Fuente AS S

ON T.IdTipoRecurso=S.IdTipoRecurso AND T.IdTipoEntidad=S.IdTipoEntidad AND T.IdEntidad=S.IdEntidad

WHEN NOT MATCHED BY TARGET THEN

INSERT ……

VALUES….

WHEN MATCHED THEN

UPDATE SET

T.Con=S.Con,

…….

 

The “issue” is going to be in the data you are using in the clause On.

As I was using a Merge statement in this case I fixed the error as show below:

ON T.IdTipoRecurso=S.IdTipoRecurso AND

T.IdTipoEntidad=S.IdTipoEntidad AND T.IdEntidad=S.IdEntidad COLLATE Modern_Spanish_CI_AS

 

Is Like make a cast between two database collations.

SQL – Saving Changes is not permitted
SQL – Saving Changes is not permitted avatar

By Leave a Comment

Have you been working on SQL Server when you realize that you need a new column in a table or make any kind of change like allow null for a specific column ?

The easy and fast way to make a change is using the design option to add the new column. Most of the time it allows you to introduce the name and the DataType you need to create.

By default SQL server, is going to show you an warning message when you committed the changes you have made in the table. The warning doesn’t allow you to save the changes and show you the follow message: “Saving change is not permitted”. The change you have made require the following tables to be dropped and re-create. You have either made changes that cant be recreate or enable the option prevent saving changes that require the table to be re-create.

This happens because SQL has activated an option by default, which doesn’t allow you to do that. in this post I am going to Show you how to change that option. However you have to be careful changing this and I recommend you just do it in a developer environment, not in production environment.

So, to change that go to Tool – Designers and Prevent saving change that require table re-creation as show the next figure: