CRM 2011 - Reports not updating - dynamics-crm-2011

I made a change to a report today that displays some financial data - it was being displayed incorrectly so I made a change to ensure it displays the correct data.
In Visual Studio the data is now correct when I run the ssrs report but when I import the report into CRM 2011 the data is still showing incorrectly as it did before.
I have checked and rechecked that the report is pointing at the same database in both instances.
I have tried everything I can think of:
Removing the field and then re-adding it
Changing the name of the field
Removing hyperlinks that were in the report
Removing a child report that was linked to the report
Any ideas what else I can try?

Really sorry to bother everybody!
It was a date issue - my local PC date is set to UK date whereas for some reason our CRM database is set to US date.

Related

We couldn't parse the input provided as a DateTime value (from SharePoint to Power BI)

I've connected Power BI to SharePoint 2010 list. and for DATE columns I got an error: "DataFormat.Error: We couldn't parse the input provided as a DateTime value.
Details:
23/03/2020"
These columns have data type both in SharePoint
and in Power BI
.
Data type is DD/MM/YYYY
what have I already tried:
Changed regional setting (on local computer and on Power BI itself) - to UK
Choose "Using local" when changed column type.
changed to text format (to split column) - nothing changed
split the column using "/" as separator
I haven't seen any other ideas in the Internet. Maybe you have other options to solve this issue.
I found answer on my question. In case anyone face same issue, I post it here:
One more thing to check in such situation is go to SharePoint settings (YourSharePointSite/_layouts/15/settings.aspx). find Regional Settings and change region there to appropriate one (with the same date format).
That's all :)
this is a nasty bug in the pbi sharepoint connector which is not in all cases able to detect/transform to correct date format. Changing API Version from 15 to 14 in M-Script does help in some cases (but not all from my experience) See also here: https://community.powerbi.com/t5/Desktop/SharePoint-Date-Data-getting-changed-in-Power-BI/m-p/736429

how do I check the last time i updated the cognos transformer?

I tried updating the cube once sometime last year and I need to know the date I did that? Is it possible to see that in the status tab in Cognos 10 administration?
If your cube is published to Cognos BI then you can easily access cube metadata using Report Expressions in Report Studio:
Open Report Studio against your Cube Package
Add a text item
Set the Source Type to Report Expression
Edit the Report Expression and use one of the cube report functions, dragging in the dimension as the parameter:
CubeDataUpdatedOn([CubeName].[DimName])
Run the report and it will give you the date on which the source cube was updated.

Sharepoint 2010 Excel Web Part displaying Pivot Table colors incorrectly

I have a Sharepoint 2010 site with an Excel Web Part being used to embed a pivot table into a page. When first set up yesterday it worked perfectly, exactly as expected. However, today one of the users clicked on the Row Labels filter button and all of the colors changed.
Above is the table is it appears in the Excel document, below is the table as it appears in Sharepoint.
http://i.stack.imgur.com/pVqGe.png
I have already tried the following fixes:
Uploaded a new copy of the excel document
Changed the theme of the table in excel
Deleted the web part from the page and recreated it
Nothing has worked.
Please help
We were able to resolve the problem by restarting the Excel Services component of Sharepoint 2010.

Crystal Reports BusinesObject Header issue

The company I'm working for has an older version of Crystal Reports before it was part of SAP, it was part of buinessobjects. We have version 11.5 of crystal reports businessobjects.
I am running into a unique issue with one report. When I schedule the report to run on a weekly basis, it adds an attachement Excel document. The issue is that the headers are missing. I have checked off the option to include headers in the attachment, but it is still not showing up.
I'm not sure why this is, because when I run the report directly in Crystal Reports, it shows the headers and I'm able to export it as an excel (data only) from Crystal Reports and the headers come accross.
It is only when I schedule the report to run it does not give the headers. I have tried all the options I can think of and done research, but the version my company is running is so old, that it is hard to find information on how to do things.
Thanks,
Dave
Are you exporting in Excel Data Only ?
When you export to Excel (Data Only), under the Excel Format Options, choose Custom.
Expand the Options.
Ensure to uncheck Simplify page headers

CrystalReports excel field cut off when using CanGrow=True

I am working on an excel report in CrystalReports, in VS2005. I have a field in the Details section which can have up to 255 characters of text, and I want the height of the row in excel to expand so that the entire text can be seen initially when the report is generated.
I set CanGrow=True in the field's properties, and the field does seem to grow; the field is only one line (Height=159), but many of the rows display multiple, wrapped lines of text. Some rows intermittently have the bottem half of the last line of text cut off; the user has to expand the row a little bit to see it. There doesn't seem to be a particular field length that causes this - in one case, it has four lines total in the output, and in another case, it has only three.
Can anyone suggest what might be the cause of this, or how I could work around it?
Thanks in advance for any help you guys can offer.
[Edit: I am no longer working on this project, so I never found out what became of this setting. Most likely it wasn't fixed, since it's not a critical issue.]
One solution to this issue that I've come up with in the past is to have two separate reports. One for display and exporting to pdfor rtf and another report for exporting to Excel.
I know in general this is not a good approach because there is the possibility for data to be different in the export than the display report, but if careful it works well.
I have a situation where a client needs data printed in a specific format on a report, but there is way to much data to physically be able to fit on a page. We worked out a solution that I run a "display version" of the report that fits most of the data, but the rest of the data necessary for there client is added only to the "Excel version" of the report.
To do this I simply load the "display report" to the report viewer as you normally would, but when you go to export the report I load the "excel report" with the same parameters as the "display report" and call the code to export the data to Excel.
By using this method the "display report" can be formatted any way necessary without having to worry about messing up the export to excel. The excel report fields can then be made a smaller size than required by the display report because the data should export even regardless of the size of the field. Doing this allows you to fit more data on the Excel export report.
Since both reports use the same datasource you will have an issue if you make a change that you have to remember to go verify the database on each report to see the new database changes, but this method allows you to include more data and in a different format than the display version of the report.
Hope this helps.
While not a solution for Crystal (I don't know of one), as part of the reporting team at GrapeCity-Data Dynamics, we've worked with similar issues taking free-form reports to excel spreadsheets for a decade. In our Data Dynamics Reports product we came up with a completely new way of solving the problem of exporting reports to excel.
We allow you to create a template for the report output. The template is a basic excel file with place holders for the various textboxes (or other controls) and regions (tables, lists, etc.) in the report. You can open this template inside of excel and modify the properties of the cells and rows. In the scenario you describe, you can export a "template" from Data Dynamics Reports and then modify the autosize property of the row in the template containing the placeholder for the textbox you're struggling with.
When you export the report to excel next time, just specify the template to Data Dynamics Reports (which can be done programmatically and transparently to the end user) and Data Dynamics Reports will honor all settings you specified in the template.
This is hard to explain so there is a ~2 minute screencast that shows this feature at our website in the following location:
http://www.datadynamics.com/Products/DDRPT/ScreencastViewer.aspx?ID=XLS01
For more information about the product and for a free trial download visit: http://www.datadynamics.com/DataDynamicsReports
Scott Willeke
GrapeCity - Data Dynamics

Resources