I am new to Kettle. Please follow me to reproduce the problem
Create a Job and drag and drop a Transfation to the design panel
Right click the Transfation and click 'Edit job entity'
'Specify by name and directory' and 'Specify by refenerce' not available in Transformation specification tab
How to resolve this problem? Thanks
Sorry for my English.
As soon as you connect to a Kettle repository via the Tools menu these controls are enabled.
answered by marabu from Pentaho forum
Related
I've been asked to make cosmetic changes to a report created by a third-party consultant on our CRM Dynamics 2011 system. The report apparently has a "report type" of "Existing File" when viewed in the "Edit" window, but has a "report type" of "Reporting Services Report" when viewed in the list of reports. If anyone can provide some clarity on this, it may be of some help.
Anyway I've been able to download the ".rdl" file behind the report and make the necessary changes (removed a paragraph in the footer). When I re-upload my new ".rdl" file and click the "Save" button, I receive the error of "You can not change the report type for an existing report". However I'm only attempting to change the report template rather than the report type.
My second strategy was to create a new report in the same way that I assume the original report was created. When creating a new report, the first option I am given is to select the "Report Type".
If I go down the path of selecting "Report Wizard Report" for the report type, then I don't get the option to select an ".rdl" file.
If I go down the path of selecting "Existing File" for the report type, then when I try and run my report it unhelpfully downloads the ".rdl" file for me! It also regards the new report as having a "report type" of "Other Report" when viewed in the list of reports.
Can anyone put me out of my misery?
Thanks in advance.
The problem with re-uploading the amended report was with the file extension of the upload.
For some reason when downloading the report file, CRM Dynamics decided to put single quotes around the file names. So instead of:
ReportName.rdl
I received:
'ReportName.rdl'
Once I removed the quotes from the file name, I was able to re-upload successfully.
I noticed that in the context menu of any connection in Azure Data Studio, there is no rename option. Also, you cannot rename the connection in the Dashboard that opens when you click "Manage" in the mentioned above context menu.
Is there any way to rename a connection created in Azure Data Studio?
Dark Templar's answer works. But you can do it inside of Azure Data Studio by adding New Connection. That opens a sidebar on the right where you can select the connection and change the any of the fields down in Connection Details. Seems like you have to press Connect to save it.
Figured out the solution. I'm on Ubuntu, and the file, where the information about connections is stored, is found in:
~/.config/azuredatastudio/User~/settings.json
Just edit the entries located in the "datasource.connections".
On Windows 10 it is under the following path:
C:\Users\<User>\AppData\Roaming\azuredatastudio\settings.json
I'm trying to add a licence.rtf file to my setup project, I've followed this stackoverflow answer step by step in order to add the licence file.
What seems to be happening is when I add the license file it doesn't add it as an embeded resource so when I remove the file from my local machine i get a complie time error...I also do not see any property which let's me change the license file to an embeded resource.
This is the error that I'm getting
Please let me know if anyone has experienced this issue before and how can I go about fixing it
UPDATE:
When you add the licence.rtf file to the Setup Project it does not have a BuildAction property which can be set to EmbededResource.Tried that
I seem to have figured it out. Instead of trying to add the License.rtf file to the setup project I've added it to another project in the solution.
Once done I reference that file in my setup project and when the setup file get's compiled the license file is embeded in the exe.
Click the file in solution explorer, view properties. Then change Build Action to Embedded Resource.
The usual way to show a license agreement in a Visual Studio setup project is as follows:
Go to the User Interface view in the IDE. Right-click "Start" and then Add Dialog, add the License Agreement dialog.
Right click the dialog to move it up or down. Right-click and Properties Windows shows properties where under License you can browse for your custom license RTF file.
There must be a way to find out who checked out the file directly in Visual Studio without having to open the VSS client and navigate to the file.
Right?
Add the SourceSafe (Soure Control) toolbar to VS. Select a file in your source tree you want to know who has it checked out and from the toolbar choose the SourceSafe Properties Icon and look at the Check Out Status Tab. :)
When you attempt to check out a file and get the error dialog indicating that the file is already exclusively checked out, if you bring up the output dialog and switch to the source control view you should see a message indicating the user id of the user who has the file checked out.
We have a 2008 solution that has a file system website as part of the solution. This solution is under source control with Team Foundation Server. Every time the solution is closed it either checks out a file called vwd.webinfo or attempts to and complains that someone else already has it checked out.
Removing the file from source control does not fix the issue because it gets re-added automatically for some reason.
Why does this happen and is there something we can do about it to remove this nag?
Thanks a lot!
open "source control explorer"
find vwd.webinfo in the correct path
click "delete"
chek-in the operation to solve this problem
The file will still be in your file system and solution, but not under source-control. You won't see "plus" or "v" or "lock" button
Go to Property Pages, select Build on the left, and uncheck "Build Web site as part of solution" Then you can delete the file and it won't get created automatically.
You should be able to delete this file manually and have it not reappear. This file holds some information that used to be located elsewhere in the project in earlier versions but apparently is not necessary. Close your solution before deleting the file from source control and on the disk.