When patching a date column with the following action
UpdateContext({MyPatch: Patch(MyTable, MyRecord, {DateColumn: Date(1970, 1, 4))})
Then the column in Azure SQL DB is updated with the correct value, but MyPatch.DateColumn is blank!
In other words, the context variable is missing the date information.
Solved! Go to Solution.
Hi Meneghino,
I can reproduce this issue on my side.
I am connecting to SQL Server On-Premise, and I have three columns in my table, Id, name and birthday.
When Patching with the following code, I can save data to the data source, and MyPatch.Id and MyPatch.name are working fine. While MyPatch.birthday is blank.
UpdateContext({MyPatch: Patch('[dbo].[a2]',{id:2,name:"ggg",birthday: Date(2017,1,4)})})
I am going to report this issue on my side. I will back once I got any response.
Thanks for your understanding and patience.
Best regards,
Mabel Mao
Hi Meneghino,
I can reproduce this issue on my side.
I am connecting to SQL Server On-Premise, and I have three columns in my table, Id, name and birthday.
When Patching with the following code, I can save data to the data source, and MyPatch.Id and MyPatch.name are working fine. While MyPatch.birthday is blank.
UpdateContext({MyPatch: Patch('[dbo].[a2]',{id:2,name:"ggg",birthday: Date(2017,1,4)})})
I am going to report this issue on my side. I will back once I got any response.
Thanks for your understanding and patience.
Best regards,
Mabel Mao
Thanks @v-yamao-msft
This is really important, also because the data in a gallery connected to the data source shows a blank after the patch operation.
Look forward to hearing back, and keep up the good work.
I am having issues as described above, has there been anything done to resolve this bug? If not, is there any work around to said bug?
I have been working on an app and wish to present it, but disappearing dates really puts a downer on things.
Thanks,
J
Hi @DrBread, sadly as I have posted elsewhere the SQL Server connector is somewhat buggy and not just in relation to dates.
However I am told by Microsoft support that some of the bugs will be fixed in July, but I am not sure which.
So I suggest you do not hold your breath and use a work-around.
I am now storing all dates as int type columns of value yyyymmdd
The reason is that this also allows for filtering of periods using > and < (which does not work with date type columns, another bug)
With this work-around I have been able to do everything I needed and not been concerned with time zone effects etc.
I hope this helps.
Hello @v-micsh-msft, I had no reply from @v-yamao-msft, so maybe you can help.
Is there any update on this issue?
Thank you.
Any updates on this, we are experiencing this as well.
User | Count |
---|---|
122 | |
87 | |
86 | |
75 | |
67 |
User | Count |
---|---|
214 | |
180 | |
137 | |
96 | |
83 |