I use the SQL 2005 row_number function to do something that sounds like what you want, in a SQL view, and then expose that as a View Form in remedy:
SELECT cast(row_number() OVER (ORDER BY somecolumn) AS int) AS Record, column2, column3..... One note, don't do this. Since the row_number is generated dynamically it is not permanently bound to a certain record unless you export it into a regular table (or a regular remedy form). I didn't think would be a problem until I found this out the hard way: Search results would sometimes display record A in the results section, and record B in the details section. This was not immediately obvious, because it only has this behavior when you have search criteria that filters some records. Hope this helps somehow! Brien On Wed, Aug 20, 2008 at 12:53 PM, Moore, Christopher Allen < [EMAIL PROTECTED]> wrote: > ** > > I have a problem creating a view form- thanks to Joe's advice I am now able > to see all the columns. My problem now is designating a key field. The > only column which is guaranteed to be unique is a GUID passed from the > external data source, but it's too long- 25 characters. > > > > Has anyone else run into this problem, and how did you get around it? I > can't use ROW_ID because this table will be overwritten monthly. I know > just enough SQL to be dangerous…is there some sort of way to add a column > and ensure it's unique via SQL? > > > > ITSM 7.0.1 p6 > > SQL 2005 SP2 > > Win 2003 svr > > > > I appreciate any advice! > > Chris > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
