Re: Row - level permissions

2015-04-10 Thread Julia James
The easiest way to allow the permissions is to add a field with the field ID 112. This is the Assignee Group. Use filters to set the Assignee Group field (Note: This shows as group names but the DB has the Group ID so all your code needs to use group ID). Give field ID 1 permissions to

Remedy 8.1.2 uninstaller issues

2015-04-10 Thread Rick Cook
I'm having a heck of a time getting ITSM 8.1.2 installed, and the Uninstaller functions DON'T seem to uninstall much of anything. Has anyone else seen this? Windows 2008, SQL. Rick ___ UNSUBSCRIBE or access ARSlist

Re: Row - level permissions

2015-04-10 Thread Jason Miller
Purely from a academic point of view, can the value of field 1 be change by a merge operation? For example importing an arx and using another field to identify a match. I haven't tried but was just wondering if that is an exception where the value can be changed. On Fri, Apr 10, 2015 at 11:26 AM,

Re: Row - level permissions

2015-04-10 Thread LJ LongWing
I don't think so...if you have a 100% incidental record with a different request id, it's a different record. I recently needed to change some request ID's (about 5 million of them)my process was to pull the entire record into an 'Entry' object, and then change the request id elements to the

Re: Row - level permissions

2015-04-10 Thread Scott Buntin
Remember migrating your code from one environment to another that Dynamic fields will need to be setup on the target environment. Field 112 is a field that is installed when AR system is installed. Not the case with other dynamic fields. Just something to remember with dynamic fields. Scott

Re: Row - level permissions

2015-04-10 Thread Mueller, Doug
No. The other criteria are used to find the record but any value of the entry ID field is ignored when it is setting all the field values (unless it is a new record in which case the entry ID is used based on the criteria you specify in the merge operation – create a new, retain old. Doug