We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Cireson Portal Request - SQL Widgets - Allow DataSource to be set
Currently SQL Widgets are only for querying the Cireson Database, which has some slight downsides because not all info is present in Cireson DB compared to SCSM Live DB. One limitation is you can't search custom relationships or custom properties because it's not in the Cireson DB.
The Widgets in particular I'd want to have this feature in order of priority:
- SQL Chart Widget
- SQL Table Widget
- SQL Count Widget
Remember if you want it to vote on it!
Comments
Great idea.
I will mention that if the database exists on the same server as your ServiceManagement db and you have access, you can use it in a query. As an example, I'm able to query my ReportServer db by specifying this in a SQL Table Widget.
select [RoleFlags] FROM [ReportServer].[dbo].[Roles]
Not as idea as being able to select the db, but it is possible.
I hope the feature includes arbitrary databases on a separate server and not locked down to scsm dbs. Can you confirm what the design plans are ?
We are currently working through the implementation details. We plan to allow administrators to enter in custom datasources by providing:
Provider (i.e. System.Data.SqlClient)
ConnectionString (i.e. Server=sql;Database=ServiceManager;Trusted_Connection=True;)
Essentially allowing the ability to query any database that you have appropriate credentials to access. The ConnectionString will of course be encrypted for the cases where a username and password is within the connectionstring.
We would love to hear your feedback and welcome any suggestions.
Thanks,
Carrie
Edit: It appears I cannot do "WITH" to predefine so I must adapt my query to maybe use subqueries instead.
Edit #2: Blah, also make sure for IN Operator that it returns a value, otherwise it may appear it doesn't work.