RE: [EXTERNAL] Re: Reporting by month value

[Reiser, John J]

Almost forgot.
For backfilling old records replace the $DATE$ string with the $3$ value 
(usually $Create Date$
Run it with an escalation that sets MM to 13 and have the filter trigger on 
modify when MM=”13”.
Then just fix the filter to run on submit with no runif qualification.


Thank you,
---
John J. Reiser
Building 760-J202
Remedy AR System Developer
Senior Software Development Analyst
Lockheed Martin - RMS Moorestown Region
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased by me

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Fawver, Dustin
Sent: Wednesday, January 31, 2018 4:23 PM
To: ARSList 
Subject: EXTERNAL: RE: [EXTERNAL] Re: Reporting by month value

LJ,

While that qualification is simple, it becomes complex for what I need.  I 
could create one that works for a few years, such as:

('Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018") OR 
('Requisition Date' >= "1/1/2017" AND 'Requisition Date' < "2/1/2017") OR 
('Requisition Date' >= "1/1/2016" AND 'Requisition Date' < "2/1/2016") OR 
('Requisition Date' >= "1/1/2015" AND 'Requisition Date' < "2/1/2015")

Do you think that’s the answer?  If so, I suppose I could use that and just 
duplicate the report for each month of the year.
Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: Wednesday, January 31, 2018 4:11 PM
To: ARSList >
Subject: [EXTERNAL] Re: Reporting by month value

Dustin,
If you are trying to do that in a Run-If or qualification, you can't use 
'functions' in those areas...you can only use them in set/push 
actionsgenerating a report for everything in January would be something like

'Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018"

The reason 'LIKE' doesn't work is because the date is stored as either the 
number of seconds since Jan 1 1970 or the number of days since 'way back' 
(don't remember the actual date)but you can only do like statements on 
strings, which it's not...so it needs to be mathematical in nature.

On Wed, Jan 31, 2018 at 2:00 PM, Fawver, Dustin 
> wrote:
Greetings!

I have a form that includes a date field.  There are records with dates 
spanning several years.  I need to generate a report that returns records that 
have a date value for a particular month of the year.  For instance, I may need 
to find records that have a date that falls in January.  I have tried the 
following qualifications to no avail.

‘Requisition Date’ LIKE “1/%”
MONTH(‘Requisition Date’) = 1
MONTH($\Requisition Date$) = 1
DATENUM(“m”, $\Requisition Date$) = 1

It doesn’t like the month or datenum functions, and it flags the first 
qualification as having an invalid date value.  I’m running this on ARS 9.1.02. 
 Smart Reporting isn’t an option since I don’t have any ITSM licenses.

Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]


--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: [EXTERNAL] Re: Reporting by month value

[Reiser, John J]

Dustin,
If you have developer control over the form you can add some hidden 
“housekeeping” fields.
I usually build a  field and a MM field on each form that will get reports 
generated.
Use functions in filters on submit to fill the fields.
Set fields action
    YEAR($DATE$)
MM (LPAD(MONTH($DATE$),2,”00”)

Then you can search for MM = “01” to get all of the January records regardless 
of the year.
You can use the  to group report data by year if you’d like.



Thank you,
---
John J. Reiser
Building 760-J202
Remedy AR System Developer
Senior Software Development Analyst
Lockheed Martin - RMS Moorestown Region
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased by me

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Fawver, Dustin
Sent: Wednesday, January 31, 2018 4:23 PM
To: ARSList 
Subject: EXTERNAL: RE: [EXTERNAL] Re: Reporting by month value

LJ,

While that qualification is simple, it becomes complex for what I need.  I 
could create one that works for a few years, such as:

('Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018") OR 
('Requisition Date' >= "1/1/2017" AND 'Requisition Date' < "2/1/2017") OR 
('Requisition Date' >= "1/1/2016" AND 'Requisition Date' < "2/1/2016") OR 
('Requisition Date' >= "1/1/2015" AND 'Requisition Date' < "2/1/2015")

Do you think that’s the answer?  If so, I suppose I could use that and just 
duplicate the report for each month of the year.
Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: Wednesday, January 31, 2018 4:11 PM
To: ARSList >
Subject: [EXTERNAL] Re: Reporting by month value

Dustin,
If you are trying to do that in a Run-If or qualification, you can't use 
'functions' in those areas...you can only use them in set/push 
actionsgenerating a report for everything in January would be something like

'Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018"

The reason 'LIKE' doesn't work is because the date is stored as either the 
number of seconds since Jan 1 1970 or the number of days since 'way back' 
(don't remember the actual date)but you can only do like statements on 
strings, which it's not...so it needs to be mathematical in nature.

On Wed, Jan 31, 2018 at 2:00 PM, Fawver, Dustin 
> wrote:
Greetings!

I have a form that includes a date field.  There are records with dates 
spanning several years.  I need to generate a report that returns records that 
have a date value for a particular month of the year.  For instance, I may need 
to find records that have a date that falls in January.  I have tried the 
following qualifications to no avail.

‘Requisition Date’ LIKE “1/%”
MONTH(‘Requisition Date’) = 1
MONTH($\Requisition Date$) = 1
DATENUM(“m”, $\Requisition Date$) = 1

It doesn’t like the month or datenum functions, and it flags the first 
qualification as having an invalid date value.  I’m running this on ARS 9.1.02. 
 Smart Reporting isn’t an option since I don’t have any ITSM licenses.

Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]


--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Re: [EXTERNAL] Re: Reporting by month value

[LJ LongWing]

that query should work, agreed it is complicated by each year you want, but
it's the best I think you can do.

On Wed, Jan 31, 2018 at 2:23 PM, Fawver, Dustin 
wrote:

> LJ,
>
>
>
> While that qualification is simple, it becomes complex for what I need.  I
> could create one that works for a few years, such as:
>
>
>
> ('Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018") OR
> ('Requisition Date' >= "1/1/2017" AND 'Requisition Date' < "2/1/2017") OR
> ('Requisition Date' >= "1/1/2016" AND 'Requisition Date' < "2/1/2016") OR
> ('Requisition Date' >= "1/1/2015" AND 'Requisition Date' < "2/1/2015")
>
>
>
> Do you think that’s the answer?  If so, I suppose I could use that and
> just duplicate the report for each month of the year.
>
> Thanks!
>
> Dustin Fawver
>
> Sr. Help Desk Technician
>
> Information Technology Services
>
>
>
> P: 423-439-4648 <(423)%20439-4648>
>
> itsh...@etsu.edu
>
> [image: itslogo] 
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *LJ
> LongWing
> *Sent:* Wednesday, January 31, 2018 4:11 PM
> *To:* ARSList 
> *Subject:* [EXTERNAL] Re: Reporting by month value
>
>
>
> Dustin,
>
> If you are trying to do that in a Run-If or qualification, you can't use
> 'functions' in those areas...you can only use them in set/push
> actionsgenerating a report for everything in January would be something
> like
>
>
>
> 'Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018"
>
>
>
> The reason 'LIKE' doesn't work is because the date is stored as either the
> number of seconds since Jan 1 1970 or the number of days since 'way back'
> (don't remember the actual date)but you can only do like statements on
> strings, which it's not...so it needs to be mathematical in nature.
>
>
>
> On Wed, Jan 31, 2018 at 2:00 PM, Fawver, Dustin 
> wrote:
>
> Greetings!
>
>
>
> I have a form that includes a date field.  There are records with dates
> spanning several years.  I need to generate a report that returns records
> that have a date value for a particular month of the year.  For instance, I
> may need to find records that have a date that falls in January.  I have
> tried the following qualifications to no avail.
>
>
>
> ‘Requisition Date’ LIKE “1/%”
>
> MONTH(‘Requisition Date’) = 1
>
> MONTH($\Requisition Date$) = 1
>
> DATENUM(“m”, $\Requisition Date$) = 1
>
>
>
> It doesn’t like the month or datenum functions, and it flags the first
> qualification as having an invalid date value.  I’m running this on ARS
> 9.1.02.  Smart Reporting isn’t an option since I don’t have any ITSM
> licenses.
>
>
>
> Thanks!
>
> Dustin Fawver
>
> Sr. Help Desk Technician
>
> Information Technology Services
>
>
>
> P: 423-439-4648 <(423)%20439-4648>
>
> itsh...@etsu.edu
>
> [image: itslogo]
> 
>
>
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
> 
>
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: [EXTERNAL] Re: Reporting by month value

[Fawver, Dustin]

LJ,

While that qualification is simple, it becomes complex for what I need.  I 
could create one that works for a few years, such as:

('Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018") OR 
('Requisition Date' >= "1/1/2017" AND 'Requisition Date' < "2/1/2017") OR 
('Requisition Date' >= "1/1/2016" AND 'Requisition Date' < "2/1/2016") OR 
('Requisition Date' >= "1/1/2015" AND 'Requisition Date' < "2/1/2015")

Do you think that’s the answer?  If so, I suppose I could use that and just 
duplicate the report for each month of the year.

Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: Wednesday, January 31, 2018 4:11 PM
To: ARSList 
Subject: [EXTERNAL] Re: Reporting by month value

Dustin,
If you are trying to do that in a Run-If or qualification, you can't use 
'functions' in those areas...you can only use them in set/push 
actionsgenerating a report for everything in January would be something like

'Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018"

The reason 'LIKE' doesn't work is because the date is stored as either the 
number of seconds since Jan 1 1970 or the number of days since 'way back' 
(don't remember the actual date)but you can only do like statements on 
strings, which it's not...so it needs to be mathematical in nature.

On Wed, Jan 31, 2018 at 2:00 PM, Fawver, Dustin 
> wrote:
Greetings!

I have a form that includes a date field.  There are records with dates 
spanning several years.  I need to generate a report that returns records that 
have a date value for a particular month of the year.  For instance, I may need 
to find records that have a date that falls in January.  I have tried the 
following qualifications to no avail.

‘Requisition Date’ LIKE “1/%”
MONTH(‘Requisition Date’) = 1
MONTH($\Requisition Date$) = 1
DATENUM(“m”, $\Requisition Date$) = 1

It doesn’t like the month or datenum functions, and it flags the first 
qualification as having an invalid date value.  I’m running this on ARS 9.1.02. 
 Smart Reporting isn’t an option since I don’t have any ITSM licenses.

Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]


--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Re: Reporting by month value

[LJ LongWing]

Dustin,
If you are trying to do that in a Run-If or qualification, you can't use
'functions' in those areas...you can only use them in set/push
actionsgenerating a report for everything in January would be something
like

'Requisition Date' >= "1/1/2018" AND 'Requisition Date' < "2/1/2018"

The reason 'LIKE' doesn't work is because the date is stored as either the
number of seconds since Jan 1 1970 or the number of days since 'way back'
(don't remember the actual date)but you can only do like statements on
strings, which it's not...so it needs to be mathematical in nature.

On Wed, Jan 31, 2018 at 2:00 PM, Fawver, Dustin 
wrote:

> Greetings!
>
>
>
> I have a form that includes a date field.  There are records with dates
> spanning several years.  I need to generate a report that returns records
> that have a date value for a particular month of the year.  For instance, I
> may need to find records that have a date that falls in January.  I have
> tried the following qualifications to no avail.
>
>
>
> ‘Requisition Date’ LIKE “1/%”
>
> MONTH(‘Requisition Date’) = 1
>
> MONTH($\Requisition Date$) = 1
>
> DATENUM(“m”, $\Requisition Date$) = 1
>
>
>
> It doesn’t like the month or datenum functions, and it flags the first
> qualification as having an invalid date value.  I’m running this on ARS
> 9.1.02.  Smart Reporting isn’t an option since I don’t have any ITSM
> licenses.
>
>
>
> Thanks!
>
> Dustin Fawver
>
> Sr. Help Desk Technician
>
> Information Technology Services
>
>
>
> P: 423-439-4648 <(423)%20439-4648>
>
> itsh...@etsu.edu
>
> [image: itslogo] 
>
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Reporting by month value

[Fawver, Dustin]

Greetings!

I have a form that includes a date field.  There are records with dates 
spanning several years.  I need to generate a report that returns records that 
have a date value for a particular month of the year.  For instance, I may need 
to find records that have a date that falls in January.  I have tried the 
following qualifications to no avail.

'Requisition Date' LIKE "1/%"
MONTH('Requisition Date') = 1
MONTH($\Requisition Date$) = 1
DATENUM("m", $\Requisition Date$) = 1

It doesn't like the month or datenum functions, and it flags the first 
qualification as having an invalid date value.  I'm running this on ARS 9.1.02. 
 Smart Reporting isn't an option since I don't have any ITSM licenses.

Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

[Ben Chernys]

Ha.  You may be right there.  Software numbering is always an arcane endeavour. 


/Ben

 

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: January-31-18 9:49 AM
To: ARSList 
Subject: Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" 
with workaround; BMC Bug raised; fix ~ 9.5

 

my hesitance regarding '9.5' specifically is surrounding that 9.5 was the 
planned version of the next version of Remedy which included Innovation 
Suitea bit over a year ago Innovation Suite was moved off into it's own 
product suite and is no longer planned to be part of Remedybecause of that 
I don't expect BMC to 'reuse' that version number at any point in the 
future...if they continue with the current numbering scheme, I expect them to 
skip 9.5 entirely and go with a 9.6 or 10.0 or something like thatbut I 
personally don't think they will use 9.5all of these statements are my own 
personal thoughts on the subject and not 'inside knowledge' of any sort :)

 

On Wed, Jan 31, 2018 at 8:26 AM, Ben Chernys  > wrote:

Hi LJ,

 

I am getting this from my client – although I was involved in the support 
ticket.  So, I didn’t hear it from the horse’s mouth.  I was told “around 9.5”.

 

It doesn’t really matter when it is fixed.  The OOTB ITSM apps generally do not 
have umlauts in the “Query Fields” defined for the forms.  Meta-Update works 
around the problem by supplying its own QueryFields list.  This bug is rare.

 

I have two clients with this problem.  One modified HPD:Help Desk’s Query 
Fields list to have fields whose values include umlauts.  The other has their 
own app.

 

In fact, it does make sense.  I have heard statements like this from many many 
software companies and I myself have made statements like this.  Remedy is a 
big piece of software and all fixes need to be tracked and scheduled.  It just 
indicates that this is currently planned to be fixed in that release.  Once it 
is assigned and investigated, times may change.

 

Cheers

Ben

 

From: ARSList [mailto:arslist-boun...@arslist.org 
 ] On Behalf Of LJ LongWing
Sent: January-31-18 8:08 AM
To: ARSList  >
Subject: Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" 
with workaround; BMC Bug raised; fix ~ 9.5

 

Ben,

Your statement regarding being fixed around '9.5' doesn't make any sense to 
medid whoever you talked to SAY 9.5 or did they say 'next release', or more 
likely 'future version'?

 

On Wed, Jan 31, 2018 at 7:59 AM, Ben Chernys  > wrote:

FYI

 

BMC has raised this as a bug and is expecting to fix it around 9.5.

 

Cheers

Ben

 

From: Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com 
 ] 
Sent: May-29-17 7:57 AM
To: 'arslist@ARSLIST.ORG  '  >
Subject: RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using 
UTF-8 on their DB on anything > 7.6.04? - "solved" workaround

 

Hi All,

 

I have heard back from the customer.  The work-around does indeed work around 
the problem.  It seems the bug is related only to building the short 
description string for an ARGetListEntry response.  The server comes back to 
the client and the client responds that it can’t decode the result (ARERR 992) 
if and only if the any of the result’s descriptions have umlauts.  

 

Meta-Update uses that string in its messaging:  Qry 1 of x: default short 
description (get fields) from the record.  Simple solution for those using the 
API is to override the default short description generation with a single field 
known to not contain any special characters such as umlauts (such as ‘1’).

 

This bug seems to have been introduced in 9.1 or at least this customer did not 
experience it before the upgrade to 9.1.0 – from which version I know not – but 
running on HP-UX. :)  I haven’t tested in on my servers (9.1.02, 8.1, …) to see 
when it was introduced and the fact that I run UTF-8 may affect the test.

 

Cheers

Ben

www.softwaretoolhouse.com  

 

 

From: Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com] 
Sent: May-25-17 9:10 AM
To: 'arslist@ARSLIST.ORG  '  >
Subject: RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using 
UTF-8 on their DB on anything > 7.6.04?

 

Hi Fred,

 

Thanks for your reply.

 

I have no access at all to the client Windows machine or the Linux server – not 
even WebEx.  As for the DB, I expect the BMC software is not lying when it 
reports its character set.  The info below is from the values of the server 
info stuff which 

RE: FYI: Duplicate Field Names in 9.1.00 201512160229 possible

[Ben Chernys]

Hi Jason,

 

I certainly recall many view generation failures at least until 7.6.04.  Back 
then if a view generation failed it did not throw an error.  That may still be 
the case.

 

Only if you used the views would you discover something amiss.  The viewname 
column was added to arschema in 7.1.  Prior to that if you needed a table’s 
viewname, you’d have to follow a DB dependent algorithm to generate it using 
the name and schemaid.

 

I’ve asked for a couple of queries to see what the view looks like.

 

Cheers,

Ben

 

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Jason Miller
Sent: January-31-18 8:57 AM
To: ARSList 
Subject: Re: FYI: Duplicate Field Names in 9.1.00 201512160229 possible

 

A bit OT but I do remember a time when you could name a field with a DB keyword 
and the SQL view would not be generated. I Remember we a few forms with the 
field call "function" and the SQL view wouldn't build until we got smart and 
started naming the field something like "functionx". I think the last time I 
saw this was like in 6.x, maybe even 5.x.

 

Jason

 

On Wed, Jan 31, 2018 at 9:37 AM, Ben Chernys  > wrote:

As I said, “I’m curious as to what field names were generated for the view.”  

I have no idea how they got it done.  I have an older dev studio and it 
prevented that action from going to the server (as it should).Remember that 
Remedy has code for generating a field’s viewname.  There’s a couple of fields 
in ITSM that have names ending in a space for example (xxx_ in the view).  A 
field could be a reserved word in the db.

Cheers
Ben

 

From: ARSList [mailto:arslist-boun...@arslist.org 
 ] On Behalf Of LJ LongWing
Sent: January-31-18 8:06 AM
To: ARSList  >
Subject: Re: FYI: Duplicate Field Names in 9.1.00 201512160229 possible

 

Ben,

I'm not sure how exactly that can happen because the 'name', assuming we are 
talking about the DB name of the field is used in the View creation, and you 
obviously can't have two columns with the same name in the DB view, so you 
can't do it in Dev Studio either...I would be curious to see a def of the form 
in questionthis hasn't been possible since I started using remedy in v 
3.2not sure how they got it done.

 

On Wed, Jan 31, 2018 at 7:55 AM, Ben Chernys  > wrote:

Hi Folks,

 Just ran into an odd issue.  A customer has created a field twice in the same 
form with the same name (but different ids).  I tried to do the same on my 
9.1.02 server using the 8.0 Developer Studio but the client prevented a 
duplicate entry into the name field.  I remember the old admin tool returning a 
duplicate field error at some point.

 I’m curious as to what field names were generated for the view.

 All workflow is keyed to field ids so it is not surprising that the Remedy 
application still functions – though I wonder which field is selected in dev 
studio.  I have downloaded the 9.1.04 clients et al and will give its dev 
studio and RDP a try if I can put in a Java it thinks is higher than 1.4 

 Alas this is mere curiosity as Meta-Update/Meta-Archive is only affected in 
that the field cache for this form is not used (a minor slow-down in 
performance when dealing with this form).

 This is not a question; it just surprised me.


 Cheers,

Ben Chernys
Senior Software Architect
  

Canada / Deutschland
Mobile:+49 171 380 2329 GMT - 7 + [ DST ]

Mobile +1 403    554 0887
Email:   Ben.Chernys_AT_softwaretoolhouse.com 
 
Web:   www.softwaretoolhouse.com

We are a BMC Technology Alliance Partner

 

 

Check out Software Tool House's free Diary Editor and our  Freebies Section for 
ITSM Forms and Fields spreadsheet.

Meta-Update  , our 
premium ARS Data tool, lets you automate your imports, migrations, in no time 
at all, without programming, without staging forms, without merge workflow. 

 

Meta-Archive   
does ITSM Archiving your way: with your forms and your multi-tenant rules, 
treating each root request as a complete tree and checking associatuions.  
Archive output to different servers, HTML pages with links to attachments or 
archive forms.

 

Meta-Databot   is 
an automated, extensible BMC Data Wizard.  It reads a file of data changes and 
sports an Undo feature.

 

Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep your 
valuable data!


  http://www.softwaretoolhouse.com/  

 

Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

[LJ LongWing]

my hesitance regarding '9.5' specifically is surrounding that 9.5 was the
planned version of the next version of Remedy which included Innovation
Suitea bit over a year ago Innovation Suite was moved off into it's own
product suite and is no longer planned to be part of Remedybecause of
that I don't expect BMC to 'reuse' that version number at any point in the
future...if they continue with the current numbering scheme, I expect them
to skip 9.5 entirely and go with a 9.6 or 10.0 or something like
thatbut I personally don't think they will use 9.5all of these
statements are my own personal thoughts on the subject and not 'inside
knowledge' of any sort :)

On Wed, Jan 31, 2018 at 8:26 AM, Ben Chernys <
ben.cher...@softwaretoolhouse.com> wrote:

> Hi LJ,
>
>
>
> I am getting this from my client – although I was involved in the support
> ticket.  So, I didn’t hear it from the horse’s mouth.  I was told “around
> 9.5”.
>
>
>
> It doesn’t really matter when it is fixed.  The OOTB ITSM apps generally
> do not have umlauts in the “Query Fields” defined for the forms.
> Meta-Update works around the problem by supplying its own QueryFields
> list.  This bug is rare.
>
>
>
> I have two clients with this problem.  One modified HPD:Help Desk’s Query
> Fields list to have fields whose values include umlauts.  The other has
> their own app.
>
>
>
> In fact, it does make sense.  I have heard statements like this from many
> many software companies and I myself have made statements like this.
> Remedy is a big piece of software and all fixes need to be tracked and
> scheduled.  It just indicates that this is currently planned to be fixed in
> that release.  Once it is assigned and investigated, times may change.
>
>
>
> Cheers
>
> Ben
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *LJ
> LongWing
> *Sent:* January-31-18 8:08 AM
> *To:* ARSList 
> *Subject:* Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; -
> "solved" with workaround; BMC Bug raised; fix ~ 9.5
>
>
>
> Ben,
>
> Your statement regarding being fixed around '9.5' doesn't make any sense
> to medid whoever you talked to SAY 9.5 or did they say 'next release',
> or more likely 'future version'?
>
>
>
> On Wed, Jan 31, 2018 at 7:59 AM, Ben Chernys  softwaretoolhouse.com> wrote:
>
> FYI
>
>
>
> BMC has raised this as a bug and is expecting to fix it around 9.5.
>
>
>
> Cheers
>
> Ben
>
>
>
> *From:* Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com]
> *Sent:* May-29-17 7:57 AM
> *To:* 'arslist@ARSLIST.ORG' 
> *Subject:* RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT
> using UTF-8 on their DB on anything > 7.6.04? - "solved" workaround
>
>
>
> Hi All,
>
>
>
> I have heard back from the customer.  The work-around does indeed work
> around the problem.  It seems the bug is related only to building the short
> description string for an ARGetListEntry response.  The server comes back
> to the client and the client responds that it can’t decode the result
> (ARERR 992) if and only if the any of the result’s descriptions have
> umlauts.
>
>
>
> Meta-Update uses that string in its messaging:  Qry 1 of x: default short
> description (get fields) from the record.  Simple solution for those using
> the API is to override the default short description generation with a
> single field known to not contain any special characters such as umlauts
> (such as ‘1’).
>
>
>
> This bug seems to have been introduced in 9.1 or at least this customer
> did not experience it before the upgrade to 9.1.0 – from which version I
> know not – but running on HP-UX. :)  I haven’t tested in on my servers
> (9.1.02, 8.1, …) to see when it was introduced and the fact that I run
> UTF-8 may affect the test.
>
>
>
> Cheers
>
> Ben
>
> www.softwaretoolhouse.com
>
>
>
>
>
> *From:* Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com
> ]
> *Sent:* May-25-17 9:10 AM
> *To:* 'arslist@ARSLIST.ORG' 
> *Subject:* RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT
> using UTF-8 on their DB on anything > 7.6.04?
>
>
>
> Hi Fred,
>
>
>
> Thanks for your reply.
>
>
>
> I have no access at all to the client Windows machine or the Linux server
> – not even WebEx.  As for the DB, I expect the BMC software is not lying
> when it reports its character set.  The info below is from the values of
> the server info stuff which Meta-Update makes available to you on startup.
> The ./arsys reports LANG, LC_ALL with en_US.UTF-8
>
>
>
> I did check on my server and was surprised that the machine, the Remedy
> user, etc seems to be on utf8 and the DB on utf16 – and a different locale
> as well.
>
>
>
> I suppose it would be easy enough to look at ITSM’s normal forms and stick
> an umlaut in one of their query results fields.  Your email has spurred
> that idea, so I thank you for that.  I am still waiting the results of the
> 

Re: FYI: Duplicate Field Names in 9.1.00 201512160229 possible

[Jason Miller]

A bit OT but I do remember a time when you could name a field with a DB
keyword and the SQL view would not be generated. I Remember we a few forms
with the field call "function" and the SQL view wouldn't build until we got
smart and started naming the field something like "functionx". I think the
last time I saw this was like in 6.x, maybe even 5.x.

Jason

On Wed, Jan 31, 2018 at 9:37 AM, Ben Chernys <
ben.cher...@softwaretoolhouse.com> wrote:

> As I said, “I’m curious as to what field names were generated for the
> view.”
>
> I have no idea how they got it done.  I have an older dev studio and it
> prevented that action from going to the server (as it should).Remember
> that Remedy has code for generating a field’s viewname.  There’s a couple
> of fields in ITSM that have names ending in a space for example (xxx_ in
> the view).  A field could be a reserved word in the db.
>
> Cheers
> Ben
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *LJ
> LongWing
> *Sent:* January-31-18 8:06 AM
> *To:* ARSList 
> *Subject:* Re: FYI: Duplicate Field Names in 9.1.00 201512160229 possible
>
>
>
> Ben,
>
> I'm not sure how exactly that can happen because the 'name', assuming we
> are talking about the DB name of the field is used in the View creation,
> and you obviously can't have two columns with the same name in the DB view,
> so you can't do it in Dev Studio either...I would be curious to see a def
> of the form in questionthis hasn't been possible since I started using
> remedy in v 3.2not sure how they got it done.
>
>
>
> On Wed, Jan 31, 2018 at 7:55 AM, Ben Chernys  softwaretoolhouse.com> wrote:
>
> Hi Folks,
>
>  Just ran into an odd issue.  A customer has created a field twice in the
> same form with the same name (but different ids).  I tried to do the same
> on my 9.1.02 server using the 8.0 Developer Studio but the client prevented
> a duplicate entry into the name field.  I remember the old admin tool
> returning a duplicate field error at some point.
>
>  I’m curious as to what field names were generated for the view.
>
>  All workflow is keyed to field ids so it is not surprising that the
> Remedy application still functions – though I wonder which field is
> selected in dev studio.  I have downloaded the 9.1.04 clients et al and
> will give its dev studio and RDP a try if I can put in a Java it thinks is
> higher than 1.4 
>
>  Alas this is mere curiosity as Meta-Update/Meta-Archive is only affected
> in that the field cache for this form is not used (a minor slow-down in
> performance when dealing with this form).
>
>  This is not a question; it just surprised me.
>
>  Cheers,
>
> Ben Chernys
> Senior Software Architect
> [image: logoSthInc-sm]
>
> Canada / Deutschland
> Mobile:+49 171 380 2329 <+49%20171%203802329>   GMT - 7 + [ DST ]
>
> Mobile +1 403  554 0887 <(403)%20554-0887>
> Email:   Ben.Chernys_AT_softwaretoolhouse.com
> Web: www.softwaretoolhouse.com
>
> We are a BMC Technology Alliance Partner
>
>
>
>
>
> Check out Software Tool House's free Diary Editor and our  Freebies
> Section for ITSM Forms and Fields spreadsheet.
>
> *Meta-Update *
> *,* our premium ARS Data tool, lets you automate your imports,
> migrations, *in no time at all*, without programming, without staging
> forms, without merge workflow.
>
>
>
> *Meta-Archive
> * does ITSM
> Archiving your way: with your forms and your multi-tenant rules, treating
> each root request as a complete tree and checking associatuions.  Archive
> output to different servers, HTML pages with links to attachments or
> archive forms.
>
>
>
> *Meta-Databot
> * is an
> automated, extensible BMC Data Wizard.  It reads a file of data changes and
> sports an Undo feature.
>
>
>
> Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep
> your valuable data!
>
>
> http://www.softwaretoolhouse.com/
>
>
>
>
>
>
>
>
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: FYI: Duplicate Field Names in 9.1.00 201512160229 possible

[Ben Chernys]

As I said, “I’m curious as to what field names were generated for the view.”  

I have no idea how they got it done.  I have an older dev studio and it 
prevented that action from going to the server (as it should).Remember that 
Remedy has code for generating a field’s viewname.  There’s a couple of fields 
in ITSM that have names ending in a space for example (xxx_ in the view).  A 
field could be a reserved word in the db.

Cheers
Ben

 

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: January-31-18 8:06 AM
To: ARSList 
Subject: Re: FYI: Duplicate Field Names in 9.1.00 201512160229 possible

 

Ben,

I'm not sure how exactly that can happen because the 'name', assuming we are 
talking about the DB name of the field is used in the View creation, and you 
obviously can't have two columns with the same name in the DB view, so you 
can't do it in Dev Studio either...I would be curious to see a def of the form 
in questionthis hasn't been possible since I started using remedy in v 
3.2not sure how they got it done.

 

On Wed, Jan 31, 2018 at 7:55 AM, Ben Chernys  > wrote:

Hi Folks,

 Just ran into an odd issue.  A customer has created a field twice in the same 
form with the same name (but different ids).  I tried to do the same on my 
9.1.02 server using the 8.0 Developer Studio but the client prevented a 
duplicate entry into the name field.  I remember the old admin tool returning a 
duplicate field error at some point.

 I’m curious as to what field names were generated for the view.

 All workflow is keyed to field ids so it is not surprising that the Remedy 
application still functions – though I wonder which field is selected in dev 
studio.  I have downloaded the 9.1.04 clients et al and will give its dev 
studio and RDP a try if I can put in a Java it thinks is higher than 1.4 

 Alas this is mere curiosity as Meta-Update/Meta-Archive is only affected in 
that the field cache for this form is not used (a minor slow-down in 
performance when dealing with this form).

 This is not a question; it just surprised me.


 Cheers,

Ben Chernys
Senior Software Architect
  

Canada / Deutschland
Mobile:+49 171 380 2329 GMT - 7 + [ DST ]

Mobile +1 403    554 0887
Email:   Ben.Chernys_AT_softwaretoolhouse.com 
 
Web:   www.softwaretoolhouse.com

We are a BMC Technology Alliance Partner

 

 

Check out Software Tool House's free Diary Editor and our  Freebies Section for 
ITSM Forms and Fields spreadsheet.

Meta-Update  , our 
premium ARS Data tool, lets you automate your imports, migrations, in no time 
at all, without programming, without staging forms, without merge workflow. 

 

Meta-Archive   
does ITSM Archiving your way: with your forms and your multi-tenant rules, 
treating each root request as a complete tree and checking associatuions.  
Archive output to different servers, HTML pages with links to attachments or 
archive forms.

 

Meta-Databot   is 
an automated, extensible BMC Data Wizard.  It reads a file of data changes and 
sports an Undo feature.

 

Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep your 
valuable data!


  http://www.softwaretoolhouse.com/  

 

 

 

 


--
ARSList mailing list
ARSList@arslist.org  
https://mailman.rrr.se/cgi/listinfo/arslist

 

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

[Ben Chernys]

Hi LJ,

 

I am getting this from my client – although I was involved in the support 
ticket.  So, I didn’t hear it from the horse’s mouth.  I was told “around 9.5”.

 

It doesn’t really matter when it is fixed.  The OOTB ITSM apps generally do not 
have umlauts in the “Query Fields” defined for the forms.  Meta-Update works 
around the problem by supplying its own QueryFields list.  This bug is rare.

 

I have two clients with this problem.  One modified HPD:Help Desk’s Query 
Fields list to have fields whose values include umlauts.  The other has their 
own app.

 

In fact, it does make sense.  I have heard statements like this from many many 
software companies and I myself have made statements like this.  Remedy is a 
big piece of software and all fixes need to be tracked and scheduled.  It just 
indicates that this is currently planned to be fixed in that release.  Once it 
is assigned and investigated, times may change.

 

Cheers

Ben

 

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: January-31-18 8:08 AM
To: ARSList 
Subject: Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" 
with workaround; BMC Bug raised; fix ~ 9.5

 

Ben,

Your statement regarding being fixed around '9.5' doesn't make any sense to 
medid whoever you talked to SAY 9.5 or did they say 'next release', or more 
likely 'future version'?

 

On Wed, Jan 31, 2018 at 7:59 AM, Ben Chernys  > wrote:

FYI

 

BMC has raised this as a bug and is expecting to fix it around 9.5.

 

Cheers

Ben

 

From: Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com 
 ] 
Sent: May-29-17 7:57 AM
To: 'arslist@ARSLIST.ORG  '  >
Subject: RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using 
UTF-8 on their DB on anything > 7.6.04? - "solved" workaround

 

Hi All,

 

I have heard back from the customer.  The work-around does indeed work around 
the problem.  It seems the bug is related only to building the short 
description string for an ARGetListEntry response.  The server comes back to 
the client and the client responds that it can’t decode the result (ARERR 992) 
if and only if the any of the result’s descriptions have umlauts.  

 

Meta-Update uses that string in its messaging:  Qry 1 of x: default short 
description (get fields) from the record.  Simple solution for those using the 
API is to override the default short description generation with a single field 
known to not contain any special characters such as umlauts (such as ‘1’).

 

This bug seems to have been introduced in 9.1 or at least this customer did not 
experience it before the upgrade to 9.1.0 – from which version I know not – but 
running on HP-UX. :)  I haven’t tested in on my servers (9.1.02, 8.1, …) to see 
when it was introduced and the fact that I run UTF-8 may affect the test.

 

Cheers

Ben

www.softwaretoolhouse.com  

 

 

From: Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com] 
Sent: May-25-17 9:10 AM
To: 'arslist@ARSLIST.ORG  '  >
Subject: RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using 
UTF-8 on their DB on anything > 7.6.04?

 

Hi Fred,

 

Thanks for your reply.

 

I have no access at all to the client Windows machine or the Linux server – not 
even WebEx.  As for the DB, I expect the BMC software is not lying when it 
reports its character set.  The info below is from the values of the server 
info stuff which Meta-Update makes available to you on startup.  The ./arsys 
reports LANG, LC_ALL with en_US.UTF-8

 

I did check on my server and was surprised that the machine, the Remedy user, 
etc seems to be on utf8 and the DB on utf16 – and a different locale as well.

 

I suppose it would be easy enough to look at ITSM’s normal forms and stick an 
umlaut in one of their query results fields.  Your email has spurred that idea, 
so I thank you for that.  I am still waiting the results of the enhancement 
(step 1) and patch (if matching the locale and charset fails) I gave the 
client.  The patch will circumvent the whole problem as the query will only 
return field 1 as its short description.

 

I am unclear what strings to set on the client for locale and charset to match. 
 In particular relating to the “iso” prefix:  de_DE.iso-8859-15 or de_DE.8859-15

 

Thanks again Fred.  I know I can count on you when it comes to Linux and 
Oracle.  Is Axton still around?  My 8.1.02, 9.1.02 servers are running that, 
though my 7.6.04 is running Windows (on XP64 I believe!) MS SQL server.  I 
upgraded a copy of 8.1 to make my 9.1.02 but I think I need to build one from 
scratch in both Linux and Windows.

 

Thanks again,

Ben

 

 

From: Action 

Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

[LJ LongWing]

Ben,
Your statement regarding being fixed around '9.5' doesn't make any sense to
medid whoever you talked to SAY 9.5 or did they say 'next release', or
more likely 'future version'?

On Wed, Jan 31, 2018 at 7:59 AM, Ben Chernys <
ben.cher...@softwaretoolhouse.com> wrote:

> FYI
>
>
>
> BMC has raised this as a bug and is expecting to fix it around 9.5.
>
>
>
> Cheers
>
> Ben
>
>
>
> *From:* Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com]
> *Sent:* May-29-17 7:57 AM
> *To:* 'arslist@ARSLIST.ORG' 
> *Subject:* RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT
> using UTF-8 on their DB on anything > 7.6.04? - "solved" workaround
>
>
>
> Hi All,
>
>
>
> I have heard back from the customer.  The work-around does indeed work
> around the problem.  It seems the bug is related only to building the short
> description string for an ARGetListEntry response.  The server comes back
> to the client and the client responds that it can’t decode the result
> (ARERR 992) if and only if the any of the result’s descriptions have
> umlauts.
>
>
>
> Meta-Update uses that string in its messaging:  Qry 1 of x: default short
> description (get fields) from the record.  Simple solution for those using
> the API is to override the default short description generation with a
> single field known to not contain any special characters such as umlauts
> (such as ‘1’).
>
>
>
> This bug seems to have been introduced in 9.1 or at least this customer
> did not experience it before the upgrade to 9.1.0 – from which version I
> know not – but running on HP-UX. :)  I haven’t tested in on my servers
> (9.1.02, 8.1, …) to see when it was introduced and the fact that I run
> UTF-8 may affect the test.
>
>
>
> Cheers
>
> Ben
>
> www.softwaretoolhouse.com
>
>
>
>
>
> *From:* Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com
> ]
> *Sent:* May-25-17 9:10 AM
> *To:* 'arslist@ARSLIST.ORG' 
> *Subject:* RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT
> using UTF-8 on their DB on anything > 7.6.04?
>
>
>
> Hi Fred,
>
>
>
> Thanks for your reply.
>
>
>
> I have no access at all to the client Windows machine or the Linux server
> – not even WebEx.  As for the DB, I expect the BMC software is not lying
> when it reports its character set.  The info below is from the values of
> the server info stuff which Meta-Update makes available to you on startup.
> The ./arsys reports LANG, LC_ALL with en_US.UTF-8
>
>
>
> I did check on my server and was surprised that the machine, the Remedy
> user, etc seems to be on utf8 and the DB on utf16 – and a different locale
> as well.
>
>
>
> I suppose it would be easy enough to look at ITSM’s normal forms and stick
> an umlaut in one of their query results fields.  Your email has spurred
> that idea, so I thank you for that.  I am still waiting the results of the
> enhancement (step 1) and patch (if matching the locale and charset fails) I
> gave the client.  The patch will circumvent the whole problem as the query
> will only return field 1 as its short description.
>
>
>
> I am unclear what strings to set on the client for locale and charset to
> match.  In particular relating to the “iso” prefix:  de_DE.iso-8859-15 or
> de_DE.8859-15
>
>
>
> Thanks again Fred.  I know I can count on you when it comes to Linux and
> Oracle.  Is Axton still around?  My 8.1.02, 9.1.02 servers are running
> that, though my 7.6.04 is running Windows (on XP64 I believe!) MS SQL
> server.  I upgraded a copy of 8.1 to make my 9.1.02 but I think I need to
> build one from scratch in both Linux and Windows.
>
>
>
> Thanks again,
>
> Ben
>
>
>
>
>
> *From:* Action Request System discussion list(ARSList) [
> mailto:arslist@ARSLIST.ORG ] *On Behalf Of *Grooms,
> Frederick W
> *Sent:* May-24-17 8:52 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT
> using UTF-8 on their DB on anything > 7.6.04?
>
>
>
> **
>
> From the bin directory, what do you get if you run
>
> > ./arsystem env | sort
>
>
>
> Look at the values of
>
>CLIENT_LOCALE en_us.8859-1
>
>LANG C
>
>LC_ALL  C
>
>
>
> What is the database character set you see when you run the following
>
> SELECT * FROM NLS_DATABASE_PARAMETERS ;
>
>
>
> We currently have a 9.1.02.003 system Red Hat Enterprise Linux Server
> release 7.2 (Maipo) (Linux 3.10.0-327.36.1.el7.x86_64)
>
> Using   NLS_CHARACTERSET   US7ASCII
>
>
>
> I have not seen your error
>
> Fred
>
>
>
>
>
> *From:* Action Request System discussion list(ARSList) [
> mailto:arslist@ARSLIST.ORG ] *On Behalf Of *Ben
> Chernys
> *Sent:* Wednesday, May 24, 2017 7:05 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT
> using UTF-8 on their DB on anything > 7.6.04?
>
>
>
> **
>
> Hi Folks,
>
>
>
> I 

Re: FYI: Duplicate Field Names in 9.1.00 201512160229 possible

[LJ LongWing]

Ben,
I'm not sure how exactly that can happen because the 'name', assuming we
are talking about the DB name of the field is used in the View creation,
and you obviously can't have two columns with the same name in the DB view,
so you can't do it in Dev Studio either...I would be curious to see a def
of the form in questionthis hasn't been possible since I started using
remedy in v 3.2not sure how they got it done.

On Wed, Jan 31, 2018 at 7:55 AM, Ben Chernys <
ben.cher...@softwaretoolhouse.com> wrote:

> Hi Folks,
>
>
>
> Just ran into an odd issue.  A customer has created a field twice in the
> same form with the same name (but different ids).  I tried to do the same
> on my 9.1.02 server using the 8.0 Developer Studio but the client prevented
> a duplicate entry into the name field.  I remember the old admin tool
> returning a duplicate field error at some point.
>
>
>
> I’m curious as to what field names were generated for the view.
>
>
>
> All workflow is keyed to field ids so it is not surprising that the Remedy
> application still functions – though I wonder which field is selected in
> dev studio.  I have downloaded the 9.1.04 clients et al and will give its
> dev studio and RDP a try if I can put in a Java it thinks is higher than
> 1.4 
>
>
>
> Alas this is mere curiosity as Meta-Update/Meta-Archive is only affected
> in that the field cache for this form is not used (a minor slow-down in
> performance when dealing with this form).
>
>
>
> This is not a question; it just surprised me.
>
>
>
>
>
> Cheers,
>
> Ben Chernys
> Senior Software Architect
> [image: logoSthInc-sm]
>
> Canada / Deutschland
> Mobile:+49 171 380 2329 <+49%20171%203802329>   GMT - 7 + [ DST ]
>
> Mobile +1 403  554 0887 <(403)%20554-0887>
> Email:   Ben.Chernys_AT_softwaretoolhouse.com
> Web: www.softwaretoolhouse.com
>
> We are a BMC Technology Alliance Partner
>
>
>
>
>
> Check out Software Tool House's free Diary Editor and our  Freebies
> Section for ITSM Forms and Fields spreadsheet.
>
> *Meta-Update *
> *,* our premium ARS Data tool, lets you automate your imports,
> migrations, *in no time at all*, without programming, without staging
> forms, without merge workflow.
>
>
>
> *Meta-Archive
> * does ITSM
> Archiving your way: with your forms and your multi-tenant rules, treating
> each root request as a complete tree and checking associatuions.  Archive
> output to different servers, HTML pages with links to attachments or
> archive forms.
>
>
>
> *Meta-Databot
> * is an
> automated, extensible BMC Data Wizard.  It reads a file of data changes and
> sports an Undo feature.
>
>
>
> Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep
> your valuable data!
>
>
> http://www.softwaretoolhouse.com/
>
>
>
>
>
>
>
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

[Ben Chernys]

FYI

 

BMC has raised this as a bug and is expecting to fix it around 9.5.

 

Cheers

Ben

 

From: Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com] 
Sent: May-29-17 7:57 AM
To: 'arslist@ARSLIST.ORG' 
Subject: RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using
UTF-8 on their DB on anything > 7.6.04? - "solved" workaround

 

Hi All,

 

I have heard back from the customer.  The work-around does indeed work
around the problem.  It seems the bug is related only to building the short
description string for an ARGetListEntry response.  The server comes back to
the client and the client responds that it can't decode the result (ARERR
992) if and only if the any of the result's descriptions have umlauts.  

 

Meta-Update uses that string in its messaging:  Qry 1 of x: default short
description (get fields) from the record.  Simple solution for those using
the API is to override the default short description generation with a
single field known to not contain any special characters such as umlauts
(such as '1').

 

This bug seems to have been introduced in 9.1 or at least this customer did
not experience it before the upgrade to 9.1.0 - from which version I know
not - but running on HP-UX. :)  I haven't tested in on my servers (9.1.02,
8.1, .) to see when it was introduced and the fact that I run UTF-8 may
affect the test.

 

Cheers

Ben

www.softwaretoolhouse.com  

 

 

From: Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com] 
Sent: May-25-17 9:10 AM
To: 'arslist@ARSLIST.ORG' 
>
Subject: RE: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using
UTF-8 on their DB on anything > 7.6.04?

 

Hi Fred,

 

Thanks for your reply.

 

I have no access at all to the client Windows machine or the Linux server -
not even WebEx.  As for the DB, I expect the BMC software is not lying when
it reports its character set.  The info below is from the values of the
server info stuff which Meta-Update makes available to you on startup.  The
./arsys reports LANG, LC_ALL with en_US.UTF-8

 

I did check on my server and was surprised that the machine, the Remedy
user, etc seems to be on utf8 and the DB on utf16 - and a different locale
as well.

 

I suppose it would be easy enough to look at ITSM's normal forms and stick
an umlaut in one of their query results fields.  Your email has spurred that
idea, so I thank you for that.  I am still waiting the results of the
enhancement (step 1) and patch (if matching the locale and charset fails) I
gave the client.  The patch will circumvent the whole problem as the query
will only return field 1 as its short description.

 

I am unclear what strings to set on the client for locale and charset to
match.  In particular relating to the "iso" prefix:  de_DE.iso-8859-15 or
de_DE.8859-15

 

Thanks again Fred.  I know I can count on you when it comes to Linux and
Oracle.  Is Axton still around?  My 8.1.02, 9.1.02 servers are running that,
though my 7.6.04 is running Windows (on XP64 I believe!) MS SQL server.  I
upgraded a copy of 8.1 to make my 9.1.02 but I think I need to build one
from scratch in both Linux and Windows.

 

Thanks again,

Ben

 

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: May-24-17 8:52 PM
To: arslist@ARSLIST.ORG  
Subject: Re: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using
UTF-8 on their DB on anything > 7.6.04?

 

** 

>From the bin directory, what do you get if you run

> ./arsystem env | sort 

 

Look at the values of

   CLIENT_LOCALE en_us.8859-1

   LANG C

   LC_ALL  C

 

What is the database character set you see when you run the following   

SELECT * FROM NLS_DATABASE_PARAMETERS ;   

 

We currently have a 9.1.02.003 system Red Hat Enterprise Linux Server
release 7.2 (Maipo) (Linux 3.10.0-327.36.1.el7.x86_64) 

Using   NLS_CHARACTERSET   US7ASCII

 

I have not seen your error

Fred

 

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Ben Chernys
Sent: Wednesday, May 24, 2017 7:05 PM
To: arslist@ARSLIST.ORG  
Subject: ARERR 91 RPC: Can't decode result - on 9.1.00; Anyone NOT using
UTF-8 on their DB on anything > 7.6.04?

 

** 

Hi Folks,

 

I have a customer using what I think of as a first.  An Oracle DB with
charset 

DB_CHAR_SET := (11) iso-8859-15

 

This is against ARS 9.1.00 201610281101 running on Linux
2.6.32-573.3.1.el6.x86_64 against Oracle 12.1.0.2.0 - 64bit Production.

 

I issue a Query and the response includes the default Form based list of
query fields.  There apparently is no way to request none.  You can override
the default which is the obvious work-around and will be tested shortly.
Presumably, you may say the 

FYI: Duplicate Field Names in 9.1.00 201512160229 possible

[Ben Chernys]

Hi Folks,

 

Just ran into an odd issue.  A customer has created a field twice in the same 
form with the same name (but different ids).  I tried to do the same on my 
9.1.02 server using the 8.0 Developer Studio but the client prevented a 
duplicate entry into the name field.  I remember the old admin tool returning a 
duplicate field error at some point.

 

I’m curious as to what field names were generated for the view.

 

All workflow is keyed to field ids so it is not surprising that the Remedy 
application still functions – though I wonder which field is selected in dev 
studio.  I have downloaded the 9.1.04 clients et al and will give its dev 
studio and RDP a try if I can put in a Java it thinks is higher than 1.4 

 

Alas this is mere curiosity as Meta-Update/Meta-Archive is only affected in 
that the field cache for this form is not used (a minor slow-down in 
performance when dealing with this form).

 

This is not a question; it just surprised me.

 

 


Cheers,

Ben Chernys
Senior Software Architect
  

Canada / Deutschland
Mobile:+49 171 380 2329   GMT - 7 + [ DST ]

Mobile +1 403  554 0887
Email:   Ben.Chernys_AT_softwaretoolhouse.com 
 
Web:   www.softwaretoolhouse.com

We are a BMC Technology Alliance Partner

 

 

Check out Software Tool House's free Diary Editor and our  Freebies Section for 
ITSM Forms and Fields spreadsheet.

Meta-Update  , our 
premium ARS Data tool, lets you automate your imports, migrations, in no time 
at all, without programming, without staging forms, without merge workflow. 

 

Meta-Archive   
does ITSM Archiving your way: with your forms and your multi-tenant rules, 
treating each root request as a complete tree and checking associatuions.  
Archive output to different servers, HTML pages with links to attachments or 
archive forms.

 

Meta-Databot   is 
an automated, extensible BMC Data Wizard.  It reads a file of data changes and 
sports an Undo feature.

 

Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep your 
valuable data!


  http://www.softwaretoolhouse.com/  

 

 

 

 

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Re: Adding WorkLog on SRM Submit.

[Kevin M Candelaria]

Hello Prajakta,
The use case is honestly the culture around here. We have a website that was 
created in Remedy 7.x era that would basically create incidents for Help 
Request and mocked up "service request" The website would then put all the user 
inputs into work logs and that's how the support staff have been looking at 
tickets for years now.

I haven't had time to work on this yet but I will eventually give it a go. It 
is currently setup using Summary and Notes fields as intended.





From: ARSList  on behalf of Advant, Prajakta 

Sent: Wednesday, January 31, 2018 4:48 AM
To: ARSList
Subject: RE: Adding WorkLog on SRM Submit.

Hi,

I agree with Carl's suggestions.
But would like to understand the use case of mapping such data in the Work info 
fields at the time of creation. Ideally, work info entries should be added once 
the request is created.

--Prajakta

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Kevin M 
Candelaria
Sent: 23 January 2018 21:34
To: ARSList 
Subject: Re: Adding WorkLog on SRM Submit.


Carl, Thanks, that's the route I wanted to take and basically set a 
qualification to only do this on Self Service reported sources incase someone 
applies a template to a new incident and the notes fields has some instructions 
it wont copy over.



I will give that a try



From: ARSList  on behalf of Carl Wilson 

Sent: Tuesday, January 23, 2018 10:43 AM
To: 'ARSList'
Subject: RE: Adding WorkLog on SRM Submit.

Hi,
A couple of suggestions:


  *   You can map the values into a Service Request field e.g. SR Type Field 1, 
and then once the Application ID is returned to the Service Request create the 
WI via custom workflow.
  *   On creation of the Incident request, have workflow on the interface 
create form that copies over the notes field into the WI fields to create the 
WI on submission.

Option 2 would be what I would suggest, it would only require a single Filter 
added to the Interface_Create form to perform this action and set the required 
WI fields on this form.

--

Kind Regards,

Carl Wilson


From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Kevin M 
Candelaria
Sent: 23 January 2018 14:56
To: ARSList 
Subject: Adding WorkLog on SRM Submit.


Hello Listers,



I am wondering if anyone can point me in the right direction, I have an SRD 
that creates an incident and I have the user inputs showing up in Summary of 
the Incident it creates an the notes field.



I would like to have that same information instead show up as a worklog, I know 
at creation it cannot do that but was wondering if anyone has any insight on 
how I can achieve that.



Thanks



[Image removed by 
sender.]

Virus-free. 
www.avast.com


-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: Adding WorkLog on SRM Submit.

[Advant, Prajakta]

Hi,

I agree with Carl's suggestions.
But would like to understand the use case of mapping such data in the Work info 
fields at the time of creation. Ideally, work info entries should be added once 
the request is created.

--Prajakta

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Kevin M 
Candelaria
Sent: 23 January 2018 21:34
To: ARSList 
Subject: Re: Adding WorkLog on SRM Submit.


Carl, Thanks, that's the route I wanted to take and basically set a 
qualification to only do this on Self Service reported sources incase someone 
applies a template to a new incident and the notes fields has some instructions 
it wont copy over.



I will give that a try



From: ARSList  on behalf of Carl Wilson 

Sent: Tuesday, January 23, 2018 10:43 AM
To: 'ARSList'
Subject: RE: Adding WorkLog on SRM Submit.

Hi,
A couple of suggestions:


  *   You can map the values into a Service Request field e.g. SR Type Field 1, 
and then once the Application ID is returned to the Service Request create the 
WI via custom workflow.
  *   On creation of the Incident request, have workflow on the interface 
create form that copies over the notes field into the WI fields to create the 
WI on submission.

Option 2 would be what I would suggest, it would only require a single Filter 
added to the Interface_Create form to perform this action and set the required 
WI fields on this form.

--

Kind Regards,

Carl Wilson


From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Kevin M 
Candelaria
Sent: 23 January 2018 14:56
To: ARSList 
Subject: Adding WorkLog on SRM Submit.


Hello Listers,



I am wondering if anyone can point me in the right direction, I have an SRD 
that creates an incident and I have the user inputs showing up in Summary of 
the Incident it creates an the notes field.



I would like to have that same information instead show up as a worklog, I know 
at creation it cannot do that but was wondering if anyone has any insight on 
how I can achieve that.



Thanks



[Image removed by 
sender.]

Virus-free. 
www.avast.com


-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist