How to know what variables can be accessed for any given screen in Mirth (v3.10)?
Eg. When setting up a Channel Source for a Database Reader connector type, I realized that I can access the variables of the fields that are being read by the SQL query when writing the Post-Process SQL query purely by experimentation (else there was nothing on the screen that would indicate that I could have done that). I see a blank box to the right of the Post-Process SQL query box, but it's empty so IDK what that's for (unlike the variables that I can drag from the right of the File Writer channel destination connection).
Looking at the "Velocity Variable Replacement" and "Variable Maps" sections of the Mirth user's manual did not have much detail on this question either.
Anyone with more experience know where I could see this information (is it a link, something in the UI itself, docs somewhere)?
Related
DS Version 11.7
In the DSODBConfig.cfg file, we set MonitorLinks=1.
The documentation tells us that this setting
Controls if stage-level and link-level statistics, and references to
data locators, are captured at the end of each job run.
But when we inspect the DSODB tables, we only find data for links that are either a data source or a data target. All data for intermediate links is missing.
Q:
Is it somehow possible to enable the logging of really all links?
Is there a way to output my SQL result directly to where screen cursor is currently. Example: If i execute "select 1" I want the result 1 to immediately populate where my cursor is (like a form fill). So if i place my cursor in an open notepad file, execute the query, it populates the 1 directly in as though "typed" in. I need to achieves this all through SQL query without C# or others.
Pretty sure many won't approve (if it's even possible) but i do have my reason for wanting to achieve this.
In short: no.
Long: I am sure you can't do this without using other programming languages.
The databases' purpose is to help application developers with storing and effectively retrieving data. So, it's kind of "utility for developers" which doesn't do anything useful without a separate (let's call it "front-end") program that inserts into and requests data from there.
My guess is you need a standalone program that wait for special key combination, asks db for data retrieval, detects active window and the element, and pastes data in there
I have a field named Datavalue 2, I have to manually assign value to that field,How do I write the calculations for this. Any leads for this will be helpful.
Thanks in advance
Tableau is a read-only tool. It does not allow you to make persistent modifications to the original source data.
If you want to derive a value of a field that can change during the life of a Tableau visualization, but leave the original data source unchanged, that is entirely possible. The Tableau features that help with this are calculated fields and parameters. Parameters can be set interactively by the user. Both features are documented in the on-line help.
Tableau has some tricky issues with it, but it is possible to work with variables as well. I am making the assumption that your data is connected through a database.
In my experience, I was connected with data from an MSSQL server, and I had need to use variables for some data cleaning.
The solution I came upon was the difference between using a 'Custom SQL Query' and 'Initial SQL'.
Tableau will not allow declared variables, temp tables, or common table expressions in 'Custom SQL' but it will allow all of those items in the 'Initial SQL' area.
Under 'Connections' Tableau should have the server connection, right clicking on this will allow you to navigate to the 'Initial SQL' box.
After that, I had to do a little fidgeting with the code, but ultimately it was a successful process. Hope that helps somewhat to the OP or any newer viewers. There weren't quite enough tags to determine more about the issue.
Whenever I construct a report that uses an embedded dataset and try to use a parameter (such as #StartDate and #EndDate), I receive an error that states I must declare scalar values. However, this error only comes up if I set a data source that uses the "credentials stored securely in the report server" option. If I set the data source to use "Windows integrated security," I do not receive the error.
I am at a complete loss. These reports need to be accessed by a large amount of people. We have granted them "browser" privileges through an Active Directory Group through SSRS, including the data sources.
What is the best way to proceed? Is there an easy fix?
I generally deploy with the option already set by going into the Data Source and choosing 'Log on to SQL Server' section > 'Use SQL Server Authentication'> (Set your user and settings). When you use a windows user as your main user after you deploy there could be issues.
The other question would be does this work correctly at all times in Business Intelligence Development Studio, BIDS, and just not on the server? It is very interesting a permission issue alone would cause a scalar error to return. Generally when users have to get to the report they may still get the error but not storing the credentials merely asks them for credentials. It would help more to know the datasets and what they are returning or supposed to be returning. Generally a Start and End are typically defined as 'DataTime' in SSRS and are in a predicate like 'Where thing between #Start and #End' and there data is chosen from a calendar by a user. If you are binding them to other datasets and there is the possibility of a user selecting multiple values that could present an issue.
I took a look at the data source that had been set up by our DBA. It was set up as an ODBC connection. I changed it to Microsoft SQL. It works now. I do not understand why and would appreciate if a more seasoned individual might explain.
I have been working with this stored procedure Sys.xp_readerrorlog for around a week now, and what I have learned is it accepts 7 parameters to fully refine how it should display its data. Easily enough to understand.
I have the question now from, where exactly does this stored procedure get its data from? I know you can also preview the data in the SSMS Object browser, under Managements In the SQL Server logs folder, although I have come to the theory that the Dialog that opens when you read the logs also use this procedure to display to the user in a grid.
I am baffled. I scouted through the system databases and found nothing (no table) which looks remotely like the output you get from this procedure
exec sys.xp_readerrorlog 1,0,'','',null,null,N'Desc';
Any expert that can tell me where the actual log data is stored, and if it is queryable through a select statement if you have admin rights?
It reads from the SQL Server error log file, which is a plain text file. There is no built-in interface to the file from TSQL; xp_readerrorlog is widely known, but it's also undocumented so relying on it is risky although of course you can use it if you don't mind that risk.
Using SMO you can find the file location but there is no special API for reading it because it's just a text file.