I have an rdlc report created in vs.net 2010 that requires the use of the lookup function available in reporting services 2008 R2 (I just assumed it would be available in the rdlc file.) This local report uses custom business objects and functionality already available within a web application, so I don't think it can be converted to a server report. The employee dataset is a list of employee objects, each object containing financial data along with office and department properties. The report is grouped by office, then department, then employee, with each employee displaying financial details. However, there is a special employee for each office that I need to display, but not include in the list of all other employees. This information needs to be displayed at the end of each office's information and I had planned on simply adding a new row to the report and using the lookup function from the employee dataset against another dataset containing the financial data for this special employee. This special employee is of the same type as a normal employee, so the lookup would be based on the office property.
So my question is, am I overlooking something or is the lookup function truly not available in the rdlc files created using vs.net 2010? If it's not available, any suggestions on how I might achieve this kind of lookup functionality?
Thanks,
Eric
Related
Good day, colleagues!
In our database all the stored procedures are binded to shemas, i.e.
Schema1.p_Procdeure1
Schema1.p_Procdeure2
Schema2.p_Procdeure1
But when I browse stored procs in Server Explorer in Visual Studio - it doesnt display shema names, i.e.
p_Procdeure1
p_Procdeure2
p_Procdeure1
It keeps sorting by schema names at first, but doesn`t display schema names! So, when you need to find exact procedure by name - you begin to suffer... Especially when there are tons of procedures...
Maybe anyone knows how to force displaying schema names in Server Explorer of MSVS?
It`s sad, but only now I noticed that schema name is displaying! But it is shown in the end of procedure name in brackets! (Unfortunately I cannot upload images)
So, the problem was in my wondrous inattention! I was looking for schema names for several hours and even started this topic!
But anyway, it will be much more comfortable and habitual if schema names will display in the begining of a string like in Enterprise Manager!
my job is to develop and manage SSRS reports.
On the enterprise SSRS server i created directories to manage permissions for different groups of users. But VisualStudio SSRS project supports only flat representation of reports. It is rather unhandy to deploy them (and become worse when they have links to each other).
Creating multiple projects is incomplete solution because of cross-directory links. It will disable preview function in report designer.
So, question is: is this possible to have equal non-flat structure both in VS project and in publicated to the server reports?
Using Geoff Hudik's method for now: http://www.geoffhudik.com/tech/2011/10/13/uploading-ssrs-reports-with-powershell.html
This is a PowerShell function that allows uploading multiple reports to ReportServer using the wcf interface, so publication can be automated.
Usage is as simple as:
UploadReports "report-server.domain.com" "c:\temp" "/TEST1/AppName"
This is my first attempt at writing a Visual Basic app using Visual Studio. I am using an Access 2013 database as the source and everything was going fine until I decided to add some calculated fields to one of the tables. Now VS is telling me that I need the "Microsoft Office 14.0 Access Database Engine OLE DB Provider" to read the tables.
I've been searching and searching but can't find anything about version 14.0 of the engine. Am I just missing something simple, or can I not access calculated fields in the DB and have to just pull the data and do the calculations in the app?
I am working on a machine with Win7 64bit, Office 2013 Pro, and Visual Studio 2015 Community.
Thanks!
EDIT: The calculated fields look like this:
"http://travellermap.com/api/jumpmap?sector="+Left([Sector],4)+"&hex="+[Hex]+"&style=print&jump=3"
Where [Sector] and [Hex] are fields in the same database. As soon as I added the fields to the database VS2015 would throw the error. If I tired use the Dataset Wizard it would tell me that there were fields in the database that were missing or could not be read without v14 of the engine.
Then even after I removed the calculated fields it still could not read the data. I have to revert to a backup copy of the database that never had calculated fields in it to get things back to working.
My exact steps were as follows:
Create database with multiple tables
Create a view that pulls together data from all the tables that I needed.
Create dataset in VS that uses that view which I called SystemMaster
Build app around it using the XAML designer
Decide that it would be quicker to use a calculated field int he DB than write the VB code to put together a URL that is needed to display an image in the app.
Close out VS2015 and laucnh Access 2013
Create the calculated field in the primary table and edit the SQL code for the view to include those fields
Save and close Access, go back into VS2015
View the dataset to see if the new fields are there, see that they are not and launch the Wizard only to find out that the Wizard says it can't access anything in that view anymore because fields are either missing or can't be read with the current version of the Access engine (12.0) and that I need version 14.0.
Search for answer, don't find one. Remove the fields from the tables and try to get back to a working application.
Realize that even after removing the fields, VS2015 won't read the tables ro views that had them.
Revert to a version of the database that did not have the calculated views, and everything works again.
While I know that the proper way to do this would be to construct the URLs in the VB code, this was easier and quicker (in theory) to do at this point which is basically a proof-of-concept/prototype.
I have a field defined in TFS so that it maps to the Finish date in MS Project. When I load the data from TFS into MS Project that field does not populate into the Finish field. However, when I populate the Finish field in MS Project and click on Publish it DOES update the field in TFS with the added/changed date.
What am I doing wrong? I mapped my ETA field to the Finished field, but when updated it only goes from Project to TFS. When I add an ETA date to something in TFS it will not populate in Project when I try to open the work item from TFS to Project.
Let me know if that doesn't make sense or if you need further clarification.
Thank you,
Shanna
This behavior is expected if the full field name you use is not the one from Microsoft.
To be clearer, if you created the field yourself with a full name you came up with: it won't be used by MS Project.
You have to just the Microsoft's field, in this case: Microsoft.VSTS.Scheduling.FinishDate for MS Project to pull the data from the Work Items when loading the MS Project sheet.
Note that you can set the relationship from WIT Field and MS Project field manually in the Team Project definition. Use the Process Template Editor (from the TFS Power tools) to do so.
More info about the Scheduling fields here
I've been using Microsoft SQL Server Management Studio for multiple manual SQL queries for Excel reports up until this point. I'd now like to automate my processes further with Microsoft Business Intelligence Development Studio and generate reports using this rather than Excel.
Here's a rough overview of what I'm looking to do:
Combine multiple data sources including SQL Server and Excel data
Generate a report using this combined data
Re-use this report in the future with different criteria and Excel data. While the SQL Server data sources would remain the same, Excel data would change for every report run.
My access to the SQL servers is read-only. I'm not an administrator on the PC I have access to due to tight security.
I've played around with both SSIS packages and reports, but am not quite sure where to begin. I did create an SSIS package that combines the SQL server and Excel data using a Merge Join transformation, but am not quite sure what to do with the created package or if that package can even be used in a report.
Any guidance would be appreciated.
Thanks.
Since you have BIDS, you have various options to send data to your users:
Create reports in SSRS
Export the SSRS report to Excel
Create SSIS packages to export CSV files that are read by Excel (I used this model to mimic the report data caching ability of SSRS)
The SQL Server Reporting Services book is a great place to start.
http://www.amazon.com/Microsoft-Server-2005-Reporting-Services/dp/0735622507