afs1jes / Clarins-US-IR-Migration

0 stars 0 forks source link

Load Mappings Table Maintenance #63

Open AVHuntley opened 1 year ago

AVHuntley commented 1 year ago

This model is a single SQL grid, presumably for writing back to this table (LoadMappings). Seems to build and submit without errors. Prod has ~300 more rows in this table than Dev does currently.

AVHuntley commented 1 year ago

Moving back to 'issues encountered' because we encountered an issue.

The Department and Brand MAP values are getting read as numbers instead of Text when they make it into Excel. This changes values of '000' to '0', '001' to '1', etc. Then, if the grid is submitted, those incorrect values make it back into the table, which requires a more technical and laborious fox.

janeslee25 commented 1 year ago

OK – we manually fixed the load templates so this issue should be corrected. We reloaded ecom and lbc – they are ok

Warm regards, Jane

From: AVHuntley @.> Sent: Monday, April 3, 2023 4:56 PM To: afs1jes/Clarins-US-IR-Migration @.> Cc: Subscribed @.***> Subject: Re: [afs1jes/Clarins-US-IR-Migration] Load Mappings Table Maintenance (Issue #63)


WARNING: External email. Please verify sender before opening attachments or clicking on links.


Moving back to 'issues encountered' because we encountered an issue.

The Department and Brand MAP values are getting read as numbers instead of Text when they make it into Excel. This changes values of '000' to '0', '001' to '1', etc. Then, if the grid is submitted, those incorrect values make it back into the table, which requires a more technical and laborious fox.

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/afs1jes/Clarins-US-IR-Migration/issues/63*issuecomment-1494968818__;Iw!!OMzJW1YBdAk!ruHdZgTzBoJ3fR67GM5TlXYBMhfQr8alnYsGXtOrXM0c7fz7tSRkAp4p7zpU9GTLXrn3wNyxhTcCGD3F8gio85af$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/A5W27ZCX5RO35ZGGZU2UXTLW7M2P3ANCNFSM6AAAAAAVMSZHHQ__;!!OMzJW1YBdAk!ruHdZgTzBoJ3fR67GM5TlXYBMhfQr8alnYsGXtOrXM0c7fz7tSRkAp4p7zpU9GTLXrn3wNyxhTcCGD3F8jzuqGUi$. You are receiving this because you are subscribed to this thread.Message ID: @.***>

AVHuntley commented 1 year ago

Okay, we've updated A3 to retrieve and paste the contents of SQL tables more accurately. On my tests, both this and the load templates are not mis-formatting the data on build.

My hope is that this fixes all load templates that were experiencing this issue and that you shouldn't have to worry about formatting the SQL grids as text in the future.

janeslee25 commented 1 year ago

it seems that many existing LBC accounts are showing as new accounts which doesnt make sense:

Image

afs1jes commented 1 year ago

It looks like this could be related to the data load problem that Rob reported earlier. Can you confirm that these new accounts have data only in April 2023 Actuals?

Thanks

Jim Schwartz Services Manager

e: @. @.> w: http://a3solutions.com http://a3solutions.com/ p: 817.705.5067

   https://www.linkedin.com/company/a3-solutions/    https://www.facebook.com/a3solutionsinc/https://twitter.com/a3_solutionshttps://twitter.com/a3_solutions

On May 9, 2023, at 11:25 AM, janeslee25 @.***> wrote:

it seems that many existing LBC accounts are showing as new accounts which doesnt make sense:

https://user-images.githubusercontent.com/124628964/237159076-62b5e10d-734c-4d5d-b20b-2e8ded06b199.png — Reply to this email directly, view it on GitHub https://github.com/afs1jes/Clarins-US-IR-Migration/issues/63#issuecomment-1540494019, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQAYMUUOP7UPIWIQPOHA43XFJVWHANCNFSM6AAAAAAVMSZHHQ. You are receiving this because you are subscribed to this thread.

afs1jes commented 1 year ago

It kind of looks to us as if these members were all created in a data load very recently…. Possibly during part of the testing that Rob was conducting yesterday (not pointing fingers, just trying to zero-in on the timing). There doesnt seem to be much data in the cube for these new accounts, but there is a little. That makes me a little worried that maybe some data made it to existing accounts and may have polluted the Finance cube. It’s easy enough to delete the newly created members, but that won’t correct for anything that was inadvertently loaded to other accounts.

I think it might be worth taking time to do a high-level reconciliation of the Finance cube, comparing it to your production cube, and seeing if you need to reload some Finance data… or maybe you’d like to restore a database backup.

Thanks

Jim Schwartz Services Manager

e: @. @.> w: http://a3solutions.com http://a3solutions.com/ p: 817.705.5067

   https://www.linkedin.com/company/a3-solutions/    https://www.facebook.com/a3solutionsinc/https://twitter.com/a3_solutionshttps://twitter.com/a3_solutions

On May 9, 2023, at 11:30 AM, Jim Schwartz @.***> wrote:

It looks like this could be related to the data load problem that Rob reported earlier. Can you confirm that these new accounts have data only in April 2023 Actuals?

Thanks

Jim Schwartz Services Manager

e: @. @.> w: http://a3solutions.com http://a3solutions.com/ p: 817.705.5067

      > On May 9, 2023, at 11:25 AM, janeslee25 ***@***.***> wrote: > > > it seems that many existing LBC accounts are showing as new accounts which doesnt make sense: > > > — > Reply to this email directly, view it on GitHub , or unsubscribe . > You are receiving this because you are subscribed to this thread. >
janeslee25 commented 1 year ago

ok - i tried to move all the new accounts to a "temp" account and then delete the temp member but it ran for almost 40mins. It seems I am not able to delete over 2000 members. what do you suggest?