Increment Refresh Duplicate row error

[Jaspal]

Morning (Odata connection)

I have a  RangeStart 01/01/2023 00:00:00 RangeEnd 31/12/2026 23:59:59

I implemented a dax fileter = Table.SelectRows(BaseOrder_table, each [SysMutationDateTime] => DateTime.AddZone (RangeStart, 0) and [SysMutationDateTime] < DateTime.AddZone (RangeEnd, 0))

With the above settings however i get error message Column 'OrderNumber' in Table 'BaseOrder' contains a duplicate value '45797.00' and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table.Cluster URI:WABI-UK-SOUTH-B-PRIMARY-redirect.analysis.windows.netActivity ID:3adda8e3-c5ea-4d02-9cb2-a1337f6190e5Request ID:60a9badf-31b9-4ca1-bf76-1deb2ec6ba6cTime:2024-04-18 01:24:37ZDetails

# Type Start End Duration Status Error

1

Data

18/04/2024, 01:01:20

18/04/2024, 02:24:37

01:23:17.031

Failed

(Show)

[Jaspal]

I cheked again and i am using inserted date and time 

[Jaspal]

Thanks for the advice i will try that

[Jaspal]

The sysmutation date was the created date unfortunately

[lbendlin]

you would need to show a bit more of your setup including an explanation of what you are trying to achieve.

[Jaspal]

I used inserted dated all working fine thanks for support

[v-xinruzhu-msft]

Hi @Jaspal 

It is glad that you solve the problem, can you provide your detail solution that more users can refer to?

Best Regards!

Yolo Zhu

[lbendlin]

Is SysMutationDateTime the right column for your partition management or is it possible that you have different values within the same order (for example if you have order line item granularity)?

The format of your order number should be Integer or text.

[Jaspal]

I changed the sys mutation date to last date change (date and Time format) and the format of order number is test running it as we speak 

[lbendlin · Accepted solution]

last date change / last modified  may not be a good candidate.  Ideally you want some immutable column like Order Create Date.