Sage 100

Oh, for Pete's sake, I give. Does anyone know any of the many discussions we've had on how to change the data dictionary so you can import into a file that Sage says you can't? I've tried numerous searches and even just tried Alnoor's postings, but I still can't find it. Foo.

Here's a word doc with some screen shot examples related to that change for CI_Item. I hope it helps

Perhaps this is what you are looking for? https://90minds-com.socialcast.com/messages/20458411

@JohnKerr - that wasn't it, but I definitely appreciate that one, too! It's a keeper. And @JeffSchwenk - that was it! I still suck at searching, in case anyone wondered.

I only found it because I copied the original (with URL) to my secret BLS KB word doc of the neatest tricks encountered since 2003. So far, Alnoor is the top contributor but there many many people attributed in it.

Oh, wait - now I read it again - this is for a FIELD. I need a FILE. @AlnoorCassim ?

File vs field is a big deal!! If there is no file you may be SOL

Evernote - How to modify VI Data Dictionaries for 4.x framework to enable import to fields otherwise defined as read only. USE CAUTION - MAKE A BACKUP DFDM MAS90\providex.ddf Lookup by name to find the VI entity to modify - get the key ID. DFDM MAS90\providex.dde Search by Key. Find the field record you want to modify Edit field 20 (15,1) a zero is importable. a 1 is read only.

Which file in the dictionary do you want to expose @BethBowers ?

@AlnoorCassim - GL_DetailPosting. I am planning on exporting out some records, using them to import into GeneralJournal to make an adjusting entry. I have a ""POSTED"" UDF in the GL_DetailPosting file and I would like to import a Y into that field once I have done the GeneralJournal import, so that the next time I export, I skip those records.

There is no business object for that and we don't want to create one, ergo no traditional V/I import possible. But here's a trick I posted way back when for @Bertowud The premise is during export of GL_DetailPosting, after a given record is exported, this Perform Logic can update UDF_POSTED to Y to that same record. If you think you can work with that where your export job selectively chooses the same records that would be hit on the General Journal posting, here are the steps: 1) Make a COPY company or at least BACKUP GL_DetailPosting. Do rest of the steps in the COPY and VERIFY it works. 2) Create your Export Job and verify it only exports the records you want (or be ready to run it in multiple passes) 3) On Configuration tab, click Perform and make it looks like this screenshot. Under CM\Script create the Performs folder. 4) Create a text file in there called UpdateGL5udf.txt and copy / paste this in there: `IF NOT(fhGL5) { fhGL5 = coSession'OpenTable(""GL_DetailPosting"", ""COMPANY"") }` `CurrentKey$ = KEC(ALT1_CH)` `SELECT *,REC=GL5$ FROM fhGL5 BEGIN CurrentKey$ END CurrentKey$ + $FE$` `GL5.UDF_POSTED$ = ""Y"" ! Repeat this line for any other UDFs you want to update` `WRITE(fhGL5, REC=GL5$) !Ok to use same channel if writing once ` `BREAK` `NEXT RECORD` `EXIT` You will have ended up exporting to a CSV file but you did nothing further with it. It was just decoration. If it doesn't make sense, send me a chat.

Genius.....That a keeper.

Groovy, @AlnoorCassim - I will test it out tomorrow!!!!!

AWESOME, worked like a champ.