- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »
Re: Add editable UDF to AR Invoice History Screen
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-14-2011 11:54 AM
Hi Guys, this is more of an FYI
SetBrowseFilter(startingValue)
Uses the startingVaule as a starting and ending portion that has to match while browsing
SetFilter(whereClause)
Creates a work table in memory that only includes the records as defined in the where clause passed into the method. This is how line entry detail tables work, once a header document is entered (ie SalesOrderNo) the SetFilter() is used to create a work table in memory that only contains the line records that belong to that header. All SetValues etc, are acted upon that work table and then when a Write() of the header is done, it commits those changes to the physical detail table.
GetResultSets(descColumn, keyColumn, resultlist, resultkeys, filter, begin, end, alternateIndex)
Reads a table applying a given where clause and beginning and ending values to form a subset of data that is passed back (resultList, resultKeys). We use this internally to load drop boxes and that type of thing, but these smaller lists have many uses.
Elliott
Re: Add editable UDF to AR Invoice History Screen
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-14-2011 12:08 PM
Thanks for the info Natasha/jepritch.
The reason I inquired about getResultSets vs SetBrowseFIlter is that, in some past projects, I've used getResultSets to say, query a history file, and depending on the amount of records in the history file, the call to getResultSets can take a while, leaving me to wait for the results with no info on the status of the call.
If the actual call of SetBrowseFilter is instantaneous, I would have no problem manually iterating through the results since I would have some idea of the progress.
Re: Add editable UDF to AR Invoice History Screen
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-16-2011 05:53 AM
I found this post, this is exactly what I need to do for a client. I have go the script working to make the field editable, but the changes are not saved to the file, is there something I am missing?
I see Justin's early post that says he was prompted to save when leaving the field, I'm not getting that result, is there another script that needs to run for each field?
Thanks for any help,
Mary
Re: Add editable UDF to AR Invoice History Screen
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-16-2011 06:10 AM
While I did get a prompt to save the changes, I didn't cofirm that the changes would actually be saved.
Now that I'm thinking about it, it wouldn't make sense if the changes could be saved if the history screen is attached to a service object.
Re: Add editable UDF to AR Invoice History Screen
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-16-2011 11:02 AM
It isn't that invoice history inquiry is attached to the service object. It is because the inquiry only has an OK button which doesn't execute the Write method. Only Accept button executes the Write method.
Sr. Software Engineer
Sage 100 ERP
Re: Add editable UDF to AR Invoice History Screen
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-16-2011 11:15 AM
The 'OK' button is only one reason. Another reason is that security is set to View Only in inquiry. The business object detects a change but it can't save the record.
Sr. Software Engineer
Sage 100 ERP
- « Previous
-
- 1
- 2
- Next »


