Upper case issue

[cmcreynolds]

Hello, I received a duplicate key error when refreshing data from SalesForce. One row had "....ELHND" and another had "....ELHNd". I am wondering which stage saw two as the same: Power Query, Power Pivot, or Excel?

We cloned the record and deleted the original and SF assigned a new and different ID.

I was just wondering if there was something I could do to prevent this from happening again?

 

[cmcreynolds]

I've thought about the surrogate numbering, but I'm pulling two objects from Salesforce with one of the IDs being "unique" (case sensitivity issue included) and another USING that ID. So, using a surrogate wouldn't work in this case, I think, because I'd have to create an additional table for converting the ID to the number Index. Or did I miss something?

As far as sharing - I'm having to share these reports on SharePoint and OneDrive with colleagues. Each report is in its own workbook.

Hope this clarifies? But thanks for the discussion, I truly appreciate it.

 

[ImkeF]

Hm, if it helps, you can create as many additional tables in Power Query as you need, no need to transfer them to Power Pivot. So the transfer to Power Pivot would be just additional numbered indexes to the existing tables.

So you'd work your way backwards then: Start with the surrogate key of those tables that are the lookup/Dim tables, so have normally just one key.

The you move on to the data/Fact tables, that have more key columns: foreign ones for the lookup-tables and their own.

 

[cmcreynolds]

Is this the same issue that I'm experiencing as far PW as rounding decimals? Just curious. I'll start a new thread if need be.

 

[ImkeF]

I'm not aware of rounding issues in PQ/PP, so you'd better start a new thread on this