merging one or more tables - excel

i'm having 6 tables in microsoft excel and i'm trying to merge them all in order to compare the records. i've tried all kinds of joins using power queries but getting null values for unmatched records. is there any way that I don't get the null values for the unmatched records rather get all the merged data at once?

Do all tables have the same structure?
If the case that the sheets have the same structure, it will be enough to always copy and paste with the option "Same as the source format (M)" In case they are different I hope you expand the information a little more so that I know how to proceed to help you. Receive an affectionate Greeting.

Related

Power Query to fetch values based on 2 criterias

I am trying to create a query based on below requirement. So far I am able to do my query based on single criteria only. Your help would be much appreciated.
1) I have opened a target workbook where I want to fetch matching values for it's two columns (temperature & density) from multiple workbooks saved in a particular folder. Here I am referring to New Query > From file > From Folder option.
2) So In my target work book I have Observed Density and Observed Temperature and now I want to extract volume and weight correction factors from a pool of mutilple workbooks picked in step 1 as mentioned above (all the workbooks in the desired folder not only have Observed Desnity and Observed Temperature but also columns contaning corresponding weight and volume correction factors in them)
That's it. Just want to know if this can be achieved using Power Query or VBA is a must do do get results? If so, any hints would be much appreciated.
I think you are on the right track. I would finish building the Query using the From Folder option to turn the data from all the workbooks into a single dataset. This query does not need to be loaded into an Excel table.
Then I would start a new query based on the 2 columns in your target workbook. They will need to be in a table or named range. In that query you can add a Merge step to match to rows in the From Folder query. Then Expand the results to add the columns you need from the matching rows.

Responsys - How to field merge multiple rows on one column using RPL?

Basically, I need to field merge a field in a certain table. Let's say TableA.Col1.
The syntax ${TableA.Col1} works perfectly. However, it only shows the first row of data in the table, whereas, I need to field merge the second row of the data as well.
Any suggestions?
I am trying like an array call ${TableA.Col1[0]} or ${TableA.Col1[1]} but no luck.
Hope to meet some Responsys guru here.
Thank you!
You need to use the <#data> directive to pull multiple records from a supplemental table. Interpolations with Table.Column syntax are designed for 1->1 relationships so will only pull the 1st record.

Missing rows when merging

I am working with Excel 2010, Power Query, and PowerPivot.
I have a query named Database that consists of 60+ merged tables containing a total of 2m+ rows. I also have a separate query that consists of two columns PrimaryKey3 and Members (a count of members per month). The entries in PrimaryKey3 are unique, consisting of ID-MMM-YY.
Both queries have PrimaryKey3 in common, however in Database there can be multiple rows with the same PrimaryKey3.
In order to match a member amount to each row in Database, I tried a Left Outer join. There were no errors, but when I try to upload to PowerPivot it says there are only 169K rows. I then tried Full Outer join and Inner Join, and received an error "could not convert value to number," coming from a column already formatted as a text in Database. This column contains numbers and numbers proceeding with a letter: 1234, A234. Every non-blank row has a PrimaryKey3. Why is it trying to reformat my columns/ how do I get around that?
Should I be using a different type of join, or is there another way besides merging to do this?
Hope this makes sense, thank you for any help in advance!
I uploaded both queries to PowerPivot, and created a relationship through PrimaryKey3. I then created a new column in Database with =Related(Enrollment[Members]).

How to merge two tables in spotfire

Hi I am new to spot fire. with spot fire (6.5 version)I have to connect to two tables which are from two different data sources. I need to create one calculated column which contains the columns from both tables. but at a time I am able to derive the formula using one data source columns only.
I need to compare the two columns from two different data sources.
When you are trying to combine data from two different data sources make sure that you have a common column to join.There is an option Insert->Columns using which you can bring columns from a different source.
Here I mentioned the steps in detail for performing the JOIN operation in spot fire.go through Spot fire JOINS operation Link.

How can I delete records from a table that have certain criteria

Rookie question I know.
I have a table with about 10 fields, one of the fields is a category field. I need this field to exist because of the multiple types of categories. However, one category in this field is wrong and is duplicating results.
So can I delete all records in the table that have "Type320" in the CatDescription field, and how? I want to keep eveerything else as it is in this table; just need to get rid of the records that have that that in that one field
Thanks very much!
EDIT: Thanks for the answer, I did not know how to do this so this is very helpful
However, this is more complicated than I thought. The raw data that I am supplied carries these duplicate records (only duplicate in certain circumstances but they are easy to isolate). This raw data is given to me on a monthly basis in several spreadsheet forms.
It all relates to these ID numbers, and has like 10 fields (xls columns). As I said before one of these is the Category Description field (sorry, this is not a lookup) In certain places this records automatically duplicates itself on output because in the database this comes from, it has to have this sub category for one particular "type"
So....every time there is a duplication, every single bit of information in all fields are exactly the same, with the exception of this CatDescription (one is Type320, and the duplicated record type is "Type321"). However, there are some instances where Type321 is valid on it's own (in which case there is no matching data row with a Type320 catdescription). By matching I mean all data in all fields of a particular record.
A very clear absolute of this is if all fields (data within) of a record with Type320 CatDescription, matches all fields (data within) a record with Type321 CatDescription, then I can delete that record containing Type321 CatDescription. This is true because this is the only situation where this duplication occurs, normally not all of this should match.
This allows all unique records with Type320 and Type321 data (that does not match exactly) to stay; just a it should. This makes sense to me (and hopefully you too :/) but can it be done, and how?
thanks because this is way over my head. I would rather know how to do it in access, but an xls solution is equally as appreciate. heck i would do it in ppt if it would get the job done! :)
I would try with one of these two querys:
DELETE FROM table WHERE CatDescription LIKE '%Type320%';
DELETE FROM table WHERE CatDescription LIKE '*Type320*';
That because the Access database engine could be using * (ANSI-89 Query Mode e.g. DAO) instead of % (ANSI-92 Query Mode e.g. OLE DB/ADO) for the wildcards.
Alternatively, this regardless of ANSI Query Mode:
DELETE FROM table WHERE CatDescription ALIKE '%Type320%';
Note the Access database engine's ALIKE keyword is not officially supported.
Does the CatDescription field look to another table? Is it a a query of those tables that creates what you call duplicate results?
If so, be careful about blaming the table that has CatDescription. Check the look-up table to see if Type320 is found there in duplicate.
If you don't have the problem isolated correctly, then you're likely to delete good records while not fixing the problem.

Resources