I want SSRS to produce a file to a specific location and send emails out to a list of recipients. The need to archive a series of reports is something everyone is interested in, we want to avoid sending out a lot of attachments, and the notification of a newly produced report adds value as well. Unfortunately, it seems I can only accomplish one or the other of these things with subscriptions.
While looking around the interwebs for the solution the common refrain is that I can accomplish one or the other, but not both. Is it a requirement that I create two subscriptions?
Short Answer
Using one subscription you cannot do that.
Workaround
If you are sure you don't want to use two subscriptions alternatively you can customize programmatically your subscription class, check this and this.
Also I recommend you check SSIS, using it you could send emails to your users when SSRS generate the file to the location.
Let me know if this helps.
Related
Is it possible to create a client-side only app, with no server backend, that stores data in a way that one user can see things stored by another user on the app?
To give some context, I am trying to create an cross platfor phone application, preferably using html, that will allow users to log their hours in a punch in, punch out style and then have these hours become viewable by a supervisor, however I will not have any server power to store any data.
I'm sure this is possible, perhaps using something like google spreedsheets or something similar to store this data, however I am at a loss how I would do this. Any help would be appreciated.
The short answer is "No."
However you can use a service such as Firebase to host your data for you.
I am developing a access database front-end, where the database resides in SharePoint list. There is a Attendance Table with AttDate and StaffID columns apart from other columns.
Want to achieve: Only one record is added per staff for a day. i.e. only One Attendance is recorded in a day. When user tries to enter attendance of same staff again on same day, he should get error.
When the back-end was in Access file, I had created an index with 2 columns, and made the index "allow unique values only". The screen looks like this.
Now when, I am moving my back-end to SharePoint, I was expecting same functionality. But, moving Tables to SharePoint using Access 2013 wizard did not create the index. Hence I thought creating it manually will solve the problem. So, I created an index with 2 columns, See screenshot below.
When I entered data, it still allows multiple values , see Screenshot
below
Please help, as to what can be the solution to this problem. I am
allowed to change existing table structure, if the solution so
demands. Any workaround will also be helpful.
SharePoint indexing is more about making it faster to retrieve and search for items in SharePoint. It has nothing to do with unique constraints.
You're going to have to add something to your SharePoint instance that will perform this check for you.
You haven't mentioned whether you're using SharePoint on-line or on-premise. You do say that you're using the Access front-end. This typically means you'll need to use an event receiver which will involve C# (or VB.NET) programming.
Workflows wouldn't prevent the duplicate row from being saved
JavaScript would help if using SharePoint UI, but won't prevent services
You do mention that you're using an Access front-end. Maybe you can add some business logic in your Access file?
Hope this helps
I have around 200 users data in my database. I have generated reports for each user containing charts and tables etc. I want to allow each user to access his or her data using URI from our mobile app. Since the users are logged in the app I dont want to relogin them on the web page.
At the moment I think i will upload the SSRS reports to the webserver and using URI users can click a link in the app to direct to their webpage and see their data.
I dont have any idea of how to achieve it. Can you please give me suggesstion on how to achieve it in the best possible way. Any links, support etc will be highly appreciate.
I'm having trouble understanding your question. Are all of these users looking at a similar report, just different data? If so, there is a UserID built in field in SSRS, and you could use that as a hidden parameter to pass to your query.
We are migrating our Hudson build tool. So, we need to have list of all users available in the existing Hudson build tool to a Excel sheet with the user name and user id's. Is there any way that I can generate a report in a single shot? Please suggest.
Into Excel? Unless you are going to write a parser yourself, forget about it. But you can still get a list of users on the system in other formats.
To get a list of all users on the system, you first have to know what your authentication realm is.
I am trying to build a user interface which will allow users to choose what kind of information they want, then based on these selected conditions, I need to query an access database and retrieve the corresponding data for future calculation. During calculation, there are two additional tables that I will query from. Finally, I need to display the calculated results to users. Now I have some questions:
Which one will be easier if I use excel as a front-end to users and retrieve querying data from Access to excel vs. I use access forms as a front-end to users and directly work with access to query data?
Does access forms can perform functions like allow users to select options from a drop down list? and once options selected, Access will query the target info?
Can Access perform intermediate calculation for large amount records? Will it get very slow? Compared to excel, which one is better in terms of calculation?
I never use Access before and just know a little about Excel VBA, not totally familiar with it, not to mention object models. So, in this case, which way is time-saving for me? or they are probably the same time-consuming?
Anything else that I should be aware of?
Thanks so much!
Bing
Definitely Access - it is specifically made for working with, querying, and reporting on data. The language of VBA that you have experience with in Excel is the exact same language used for coding in MS Access!
Access, no question!
Absolutely. Of course it doesn't magically know this as your requirement. You have to drop the combo box on the form yourself, and then in the OnChange event of the combo box, alter a query statement that displays results to filter based on the user's selection.
Sure. Make a temp table (a table that is only used for the calculation), populate the records with INSERT statements, apply intermediate calculations with UPDATE statements, and display the results. Access is built for this kind of thing and will most likely be faster than Excel.
Access uses VBA as well. There may be a larger learning curve to switch, but if you are familiar with the user interface objects in Excel such as Button, Combo Box, etc., they will be very similar and yet more intuitive in Access (Because that's what Access was made for)
Access has some quirks. Google a few tutorials and get some background on the ways Access is traditionally used for your kinds of scenarios and it will go a long way toward streamlining your development.
Start with the simplest model that will accomplish what your requirements are, and implement it. Then work through the quirks and bugs that you find with Google as your friend, and you should be able to get something solid pretty quickly! As you get into the experience, feel free to post new questions with specific problems you find along the way.
Best Regards,