Sage 100

Long story short, I mistakenly reinitialized BM_ProductionHistoryTierDistribution.M4T instead of BM_ProductionTierDistribution.M4T on a client system last week.  Is it possible to open that table up to import records back into it?  @Alnoor Cassim?  I know there's a data dictionary hack you can do to import into some files (which I haven't had time to search for yet); has anyone tried it with this file (fingers crossed)?​

------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems
San Jose CA
800.627.9032 x221
------------------------------

Not possible to restore that file from a backup??

------------------------------
Therese Logeais
Technology Integrators
------------------------------

That hack doesn't apply here. In the dictionary that table is specifically excluded from V/I import and also doesn't have a direct business object. It's similar to how you can't import directly into GL_DetailPosting but just as there are tricks for updating that (and I posted one awhile back), there is for this table as well. The key question is if you were able to import, at this time do you have the LotSerialNo available?

Several approaches and probably No 3 is your best bet:

1. V/I export out of BM_ProductionHistoryDetail while Perform Logic can simultaneously write/update BM_ProductionHistoryTierDistribution. That was my GL_DetailPosting trick.
2. An MD type can create a _bus object for BM_ProductionHistoryTierDistribution and make it available for V/I import. Have done that too.
3. Selectively restore this file / table from backup. But If you think that would overwrite the data that's currently in there since you reinitialized, you could restore to a different company code then merge the restored file into the live file. If you're on SQL that's pretty straightforward. If non-SQL, an MD types can write a short spin program to merge it for you.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------

I'll need to find out how current a backup of the history file I have.  They do many production entries daily, so I would need to merge current records with the old ones.  They are on version 4.5.5 Advanced, no SQL.  Thanks for the responses.  Checking with my colleague Nicole Ronchetti to see if she can help me out of this mess.

------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems
San Jose CA
800.627.9032 x221
------------------------------

Original Message:
Sent: 03-21-2019 13:46
From: Alnoor Cassim
Subject: Restore data into BM_ProductionHistoryTierDistribution.M4T?

That hack doesn't apply here. In the dictionary that table is specifically excluded from V/I import and also doesn't have a direct business object. It's similar to how you can't import directly into GL_DetailPosting but just as there are tricks for updating that (and I posted one awhile back), there is for this table as well. The key question is if you were able to import, at this time do you have the LotSerialNo available?

Several approaches and probably No 3 is your best bet:

1. V/I export out of BM_ProductionHistoryDetail while Perform Logic can simultaneously write/update BM_ProductionHistoryTierDistribution. That was my GL_DetailPosting trick.
2. An MD type can create a _bus object for BM_ProductionHistoryTierDistribution and make it available for V/I import. Have done that too.
3. Selectively restore this file / table from backup. But If you think that would overwrite the data that's currently in there since you reinitialized, you could restore to a different company code then merge the restored file into the live file. If you're on SQL that's pretty straightforward. If non-SQL, an MD types can write a short spin program to merge it for you.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------