That is correct. Well, current timestamp (includes time too) The getdate
function in SQL Server (don't remember you saying which DB you are using).
https://docs.microsoft.com/en-us/sql/t-sql/functions/getdate-transact-sql
"Returns the current database system timestamp as a datetime value without
Thanks a ton for your superb response.
Also regarding the DATEDIFF() - > please could you let me know that are you
calculating it for the difference between Submit Date & current date??
--
Sent from: http://ars-action-request-system.1.n7.nabble.com/
--
ARSList mailing list
ARSList@arslist
Thanks a ton Jason.
Also i will try to impalement it & will keep you posted on it.
One query -
Also after adding the custom column in "U__HPD_Help_Desk" is it mandatory to
add the dummy columns to every other view used in the Overview UNION view.
After that we need to simply add the new colu
I am off to bed so I'll be a little sparse on the detail in this reply...
The DB view U__HPD_Help_Desk is an out of the box view, I only added a
column to it. That view and one for each of the other forms Change,
Problem, Work Order, Task, etc. also have similar out of the box DB views.
When all i
Thanks a ton Jason for your superb response.
I am trying to summarize it in detail:-
You created a new DB view & added the custom field for the aging calculation
in it.
After that how to retrieve it in overview console table??
Also even after adding the custom field in the overview console tabl
Thanks a lot Jason for your super detail response.
i believe you are talking about DB view & created a custom view
-"'U__HPD_Help_Desk' DB view" which is accommodating the "zDATEDIFF" with
the aging calculation.
So after that you want that custom - "zDATEDIFF" to be extended on to the
overvi
Thanks LJ for your response.
Please could you elaborate more on the same as you have already achieved it
earlier.
Early response will be highly appreciated.
--
Sent from: http://ars-action-request-system.1.n7.nabble.com/
--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/
and I know it's possible to add columns to that tableI know it's
complex, and your workflow will need to be equally complex to accommodate
the complexitiesbut that's how I've done it in the past.
On Tue, Feb 6, 2018 at 12:09 PM, Abhi$hek wrote:
> But LJ the table is overview console tabl
But LJ the table is overview console table only which is a bit complex one
and we need to show the incidents aging in it.
On 06-Feb-2018 11:04 PM, "LJ LongWing" wrote:
> It's not too complicated
>
> 1 - Create a display only field on the form that contains the table field
> 2 - Add that column a
It's not too complicated
1 - Create a display only field on the form that contains the table field
2 - Add that column as a column in the table
3 - Write an AL Guide that loops through the table and does the calculation
needed, and sets the column in the table with the value you want, looping
thro
Can you please provide detail on how to achieve it and show the aging in
the overview console table .
On 06-Feb-2018 10:49 PM, "Dave Shellman" wrote:
> If you need to make the calculation and it needs to be current, the only
> logical trigger is with the table refresh.
>
> Dave
>
> On Tue, Feb 6
If you need to make the calculation and it needs to be current, the only
logical trigger is with the table refresh.
Dave
On Tue, Feb 6, 2018 at 1:29 PM Abhi$hek wrote:
> We can consider simple hours as well.
>
> On 06-Feb-2018 10:02 PM, "Dave Shellman" wrote:
>
>> Sort on Submit Date/Time will
We can consider simple hours as well.
On 06-Feb-2018 10:02 PM, "Dave Shellman" wrote:
> Sort on Submit Date/Time will rank the records which is used in the aging
> calculation.
>
> Should the aging calculation use business time or simple hours open? If
> business time then holidays would need t
Sort on Submit Date/Time will rank the records which is used in the aging
calculation.
Should the aging calculation use business time or simple hours open? If
business time then holidays would need to be considered which leads to
regional holidays in a global environment.
Dave
On Tue, Feb 6, 2
Once case where you can see drastically different out of order Case ID's in
a server group is if Incident(s) are created on a non-user facing admin
server that has been up for a while (months). An example is UDM is used to
create a bunch of request for a project and the admin server is used for
th
Thanks JD for your kind response.
But we need to show the aging in numbers as well so that support staff can
take proper action as per the aging.
On 06-Feb-2018 6:31 PM, "JD Hood" wrote:
> If you just want the incident table sorted in order of older INC's at the
> top, you can sort by incident I
If you just want the incident table sorted in order of older INC's at the
top, you can sort by incident ID# or Submit time and accomplish that. No
workflow or fields needed, just a wee bit of training. Standard column sort
behavior should already work on the table -- click the Inc# column header
to
then setup a filter to show
open 5 days or more, open 5 days but less than 7, and/or open over 7 days.
Brian
From: ARSList on behalf of Abhishek2019
Sent: Tuesday, February 6, 2018 6:32:50 AM
To: arslist@arslist.org
Subject: Re: How calculate the Aging of an
Hi JD,
Thanks for your kind response.
The requirement is just to show the older/aged incidents on top of the
overview console table for the support staff attention only to proactively
manage the SLA.
I can create a custom field in hpd:help desk which will calculate the
DATEDIFF for the submit da
Hi JD,
Thanks for your kind response.
The requirement is just to show the older/aged incidents on top of the
overview console table for the support staff attention only to proactively
manage the SLA.
I can create a custom field in hpd:help desk which will calculate the
DATEDIFF for the submit da
Hi AA,
Presuming I understand correctly and the main point of the business
requirement is to just prioritize the aged incidents first in the Incident
table on the overview console, then couldn't you just sort the table by
Incident Number? Granted with blocks of ID's and a high ticket flow it is
po
Thanks for your kind response.
As the requirement is to show the Incident Aging in overview console table
only so i doubt DB View will not suffice it. Also please could you elaborate
it more as what will be the trigger point(Execute on condition) for the
Custom field calculation on the DB view.
Thanks JD for your kind response.
Please could you elaborate on your first approach to achieve it via AL.
Escalation can be created for it but suppose my escalation run every mid
night then the incidents raised after mid night will be missed during
calculation
Also the motive of business is too
Aging can be done through the "Modulus" function. "%" Do something like
Days % 5 to have something fire every 5 days (Business Week). Or Days % 30
for every month.
Of course you need to compte "Days" using something like
((($TIMESTAMP*60)*60)*24) or something like that. Or use a built in functi
Personally I would look at it a bit differently. Since you need to do some
DB view work in order to add custom fields anyways, I would consider doing
the age calculation as a new column in the DB view and then expose that as
a field in the Overview Console.
Since the Overview Console tends to be o
Hi AA,
Off the top of my head, you are looking at either adding a "Refresh Aging"
button on the console and/or firing an active link on Window Open/Display
to trigger the stack of workflow needed to re-calculate the field/column on
each Incident record and then refresh the table at the end. The wo
Yes it should be.
--
Sent from: http://ars-action-request-system.1.n7.nabble.com/
--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist
yes it should be updated on overview table refresh whenever support staff
logged in.
--
Sent from: http://ars-action-request-system.1.n7.nabble.com/
--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist
Is this "Aging" value required to update and be displayed in real-time
whenever support-staff open/refresh the Incident table in the Overview
console?
Thanks,
-JDHood
On Mon, Feb 5, 2018 at 2:42 AM, Abhishek2019 wrote:
> Hi Experts,
>
> We are having a requirement to shown the Aging of an Incid
Hi Experts,
We are having a requirement to shown the Aging of an Incident in the
overview console.
I am able to add the custom field in overview console but my issue is stated
below:-
I am trying to use the DATEDIFF function to calculate the Aging of an
incident on the basis of (Submit Date of
30 matches
Mail list logo