What object are you using to modify GL_DetailPosting?

I get the same result with all the ones listed in File Layouts:

GL_GeneralJournal_upd
GL_RecurringJournal_upd
GL_AllocationJournal_upd
GL_TransactionJournal_upd
GL_DailyTransaction_upd

Ah, that explains a few things.  Generally, the _upd objects are not business objects so they do not have the functions like SetKey(), SetKeyValue(), SetValue(), Find(), Write(), etc.  That is why you are receiving strange errors.  Generally, scripting using these objects is minimial.  You can instantiate them and maybe run the associated register and update, but you can't really alter the data in that manner.

The file layouts list these more for help with UDF data flow.  SetKeyValue(), Find(), GetValue() are functions available for _svc objects and SetKey(), SetValue(), and Write() are functions available for _bus objects.

Hope that helps

Elliott

Thanks Elliot. Would you say in general that any table without a _bus object is not editable?

Yes that would be a great way to put it.  You require a _bus object to add/modify data in a table using scripting.

I suggest then that the "File and Table Listings" not list objects without a "_bus" suffix as "Bus Obj:"

Thanks connex.  I think that listing is basically a massaged dump of the dictionary where the list of business objects reside includeing the _upd ones.  These are used as I said earlier for mapping of UDFs, but I'll see what we can do as far as changing that listing.

Elliott

Thanks connex.  I think that listing is basically a massaged dump of the dictionary where the list of business objects reside includeing the _upd ones.  These are used as I said earlier for mapping of UDFs, but I'll see what we can do as far as changing that listing.

Elliott

I suspect that listing is generated from the content in the data dictionary and I don't think it is worth stripping those out with special logic.  As mentioned, I think the surefire way to identify if you can use a specific class to modify records in a given table is to see if the table has a class that ends with _bus. 

Another approach is to try to create a VI job for the table and if it isn't available then there isn't a _bus class you can use (it seems VI checks the tables custom attributes to locate a class that ends with _bus in addition to checking of the "Exclude From V/I" option is checked). 

One other approach is to traverse the classes to see if the target class inherits SY_Maint as this is the class that contains the SetValue, SetKeyValue, and SetKey methods.  SY_Service contains the SetKeyValue and Find methods.  SY_Maint inherits SY_Service.