Sage 100

Anyone know if there is a way to import into business framework ""hidden"" fields? Specifically, I need to import into the BM_BillDetail.BillType field because of a program defect back in 2015.2 for 40,000 records, but that field is not available in VI, and there is no way I'm correcting in DFDM! TIA!

You could do it with some relatively simple PERFORM logic called from your V/I job, perhaps. My first thought was to tell you that a developer could do it for you.

I would get a programmer and have a small spin program done to deal with this, I agree with Philip.

in 2018.3, if you update the bill type of the component bill's bill via bill maintenance, it updates all bill detail records' bill type where it is used as a component. This behavior can be verified by viewing BM_BillDetail in DFDM and making and reverting the bill type for a given sub-assembly. So you might be able to accomplish this with a VI job with a source file containing the bill twice, and only import into BM_BillHeader, you should only need the minimum required fields and then the BM_BillHeader.BillType field. In the source file, the first record for a bill can have a bill type value for maybe I or E, just to make sure it is changed at least once, and then the second record for a bill can have the intended value for the bill type. Haven't tested this but in theory, it should do what you need it to.

I've used these steps (Alnoor's) to make unavailable fields available in VI such as Quantity Received in Purchase Order. Hopefully it works for you! 1. DFDM MAS90\providex.ddf 2. Lookup by name to find the VI entity to modify. Then change the default to get the key ID. 3. DFDM MAS90\providex.dde 4. Search by Key. Find the field record you want to modify 5. Edit field 20 (15,1) a zero is importable, a 1 is read only.

I appreciate the quick responses, and special thanks to David and Kate - I will try those suggestions. Kate, I recognize that now...I did that to the IM_ItemWarehouse many years ago but never saved the steps. I will now!

Changing the data dictionary via the @AlnoorCassim method is a popular way to go. Jus remember that it gets reset every time you do an upgrade.