I had to change some of the column lengths in the source to a higher value in information, but I am still getting the same length as below and it looks like it was not updated. source and target are both oracle tables. Do I need to reimport source tables in information after changing column names?
Thanks in advance
You need to propagate the change across your mapping. Just right click on the attribute and select Propagate Attributes
Related
This happened when updating text area.
If you have a valid EF model with the correct field length, this shouldn't be a problem (for example, by decorating with Length attributes)
This type of error generally occurs when you try to put characters or values more than what you have specified in your table schema.
Like in that case: you specify varchar(10), but you are trying to store a value that contains 19 characters.
Solution:
Check your parameter sizes against column sizes and the field(s)
Try updating each property one by one with a .SaveChanges() to find out which one is causing the error.
Sample Sheet
How do you reference the Data Import tab and display everything in order of most recent date at the top within the Worksheet, and alphabetize the Vendor Name (column C - Worksheet)?
I have tried the SORT function but little to no luck as it just alphabetized everything in order even when referencing the Import Date from the Data Import.
For visual reference
FIGURE 1:
FIGURE 2: Expected Outcome
To further elaborate:
This one might be tricky, but Column B will be hyperlinks and also needs to be in the correct order that also belongs to its proper data brethren. This is what I currently have and just references everything in order of new data incoming.
(=ARRAYFORMULA(IF('Data Import' !A:A<>"", HYPERLINK("Some_Website" & 'Data Import'!A4:A&, 'Data Import'!A3:A), ""))
This one I'm guessing will not only need to reference the date, but the naming order as well.
Okay. So this was resolved with the query function.
Source info: https://support.google.com/docs/answer/3093343?hl=en
The sample sheet will remain open to those who are in need of knowing how to use it and can view how it was used.
Doing this resulted in the expected outcome. However, there is an issue.
If you have other columns you intend to put manual data entry, this entry data will remain stagnant and will not move.
Only the columns with the query formula will be dynamic and will keep getting pushed downward while your stagnant entries will remain right where they are.
I'm currently looking into Assigned Index Numbers to resolved this.
Solving the Dynamic / Static Data Alignment challenge using Alignment Index Numbers
I have a resource allocation report that automatically generates each week based on a bunch of monthly data. The data is summarized in a PivotChart with slicers for different column values (Name, Role, Project, etc). The chart shows the units allocated for each role, for each month for the next 13 months:
Resource Allocation PivotChart
Basically, I want to add a target line to this chart. I've tried a couple different things.
With other projects, I've succeeded in adding a target to PivotTable data by adding the target value in a column next to the PivotTable, but that won't work with this report because that method forces me to use a regular chart instead of a PivotChart so I can't have the slicers (which I need), and the PivotTable changes shape a lot so it would overwrite the data as different slicer options are selected and as new values are added to the data each week.
The closest I've gotten to adding the target into the chart is by actually creating a new line item where the Role is "Target" and the value for each month is the target value: Target line item. I can even change the data series type to look like a target line: PivotChart with target line. The only issue is that "Target" now shows up in the role slicer.
Is there any way to hide "Target" from the Role slicer when it HAS data? Or is there some other way to add a target line to this PivotChart?
You could create a grouping column where RoleGroup is the same for both the Role and the Target, and use that for your slicer instead. That way you are effectively selecting Role and Target at the same time for any set of values.
Another alternative would be to convert your data to a "long" format, that looks something like below, and then you can drop Value and Target on the Measure shelf of the pivot table:
I have a problem with the "Transformer"-State in the DataStage Designer (version 11.5).
I want to import a table and export only selected columns.
It works without errors with a sequential file. But when exporting to a table, the entire table is transferred and not just the selected columns. The mapping of the columns in the Transformer-State is the same for both variants.
Does anyone know this error and how to fix it?
Thanks.
If I get you right you try to move only a subset of columns from one table to another.
My first advise would be to limit the the number of columns you select in the ImportDB_Table source stage.
Regarding your problem - RTC (Runtime Column Propagation) could be the reason that you see more columns in the output. RTC will dynamically map all columns from the input and you have to explicitly specify only those columns which a treted in a special way.
Check out the job properties oif runtime column propagation is enabled and disable it.
Disable also the RTC setting within the TRANSFORMER stage - found in the Transformer stage properties.
I am new to PowerBuilder and I need to add a new column to a DataObject. The DataObject has several fields which retrieves data using select statement. So if I add a column in the select statement I get another field with a name compute_0041 along with the added column field. When i try to remove the compute_0041 field I cannot see any value in the field representing a new column. How do I remove the compute_0041 that gets automatically added?
Thanks
In Datawindow if you accidentally put a 0 or '' in one of the rows in the tab called Computed Columns then these columns may come in. Of course, you can also have a computed column yourself by specifying it there but since it seems you think you didnt do anything and it came up on its own it appears to be an accidental issue.
You can of course check for it by going to the SQL mode and checking for it there. Also, the last tab in the design view it shows the complete generated SQL where you can easily see a select column that is not chosen by you.
Hope the above will aid you to identify the issue. Please let me know if you still have the issue.