How do you use report filters with date and time fields?


We have an issue from a user where he mentions that “Report filters for dates are not displaying properly”. This issue is happening when the user is using the triCreatedSY field in user filters. I added a date-time field to an existing report and chose the filter of “After”. When I run the report, the filter says “Contains” that also does not work. I entered the date of one of the items in the report and it did not return that item…

The system is providing the filter operator similar to the date fields, but it is not working no matter what date we give or what operator we use. We tried the same for other date fields which ends with “DT” but those work fine. I looked in the field properties of the triCreatedSY field and found the property “Sub Attribute Type = Created DateTime (Number)”. In the TRIRIGA user guide (PDF), I found the following information…

My understanding is if the user wants to use the triCreatedSY field, then we have to add a field “Created DateTime Number” on the BO. Based on the PDF, when I added a field on the BO, no information is getting populated in that field. It looks like there should be a way to map it. Is my understanding correct? Will it be a good solution to apply the changes as mentioned in the user guide? Or can we suggest an alternative to the user?

The triCreatedSY field is actually a timestamp field, so it acts like a string. You’ve started in the right direction by creating a new Created DateTime field, but it needs to be a Field Type = “System Read Only” and the Sub Attribute Type = “Created DateTime (Number)”. Note that previously created records will not have this field populated.

[Admin: To see other related posts, use the Filter tag or Date tag.]

Continue reading

Advertisements

How do you populate or update dates stored as numeric values?


I added a new date field, cstReminderDateDA, to a custom business object. For existing records, there is a requirement that cstReminderDate be set to the value of an existing date field (cstDueDateDA) minus 30 days, i.e. cstReminderDateDA = (cstDueDateDA – 30). This would be pretty straightforward, except that both cstReminderDateDA and cstDueDateDA are stored as numeric fields in our Microsoft SQL Server database. How do I populate cstReminderDateDA?

IBM TRIRIGA stores the date as epoch time. See the following wiki link explaining this. If you do some searching, you will find some functions available for SQL Server for data calculations.

[Admin: To see other related posts, use the Epoch Time tag.]

Continue reading

How do you use fields that refer to Current Date or System Date?


What is the best way to handle calculated fields that need to reference the Current Date or System Date? For example, I have a number field in the Building BO called Building Age. To calculate the Building Age, I had to create another field called “cstCurrentDateDA” to store the current date the Building record was created.

From there, I take the Current Date minus the In Service Date of the building. However, let’s say I wanted the Building Age field to get updated daily. In my current design, I would have to probably create an asynchronous workflow to update the “cstCurrentDateDA” field and then trigger a Save action to get the extended formula against the Building Age field to fire.

Is there a better approach to dealing with field variables that rely on the Current Date or System Date? Instead of creating a custom field to store the Current Date to act as a constant factor?

[Admin: To see other related posts, use the Date tag.]

Continue reading

Can you retire a job plan to get rid of unneeded draft work tasks?


When the Operations team was changing a job plan, the wrong date was entered, and it created over 1,800 work tasks. They have since tried to retire them and they changed to Draft status. To get rid of these, can the job plan itself be retired?

[Admin: To see other related posts, use the Job Plan tag.]

Continue reading

IV97769: Filtering on a word in date column gives unexpected results


Filtering on a word in a date or date-time column produces unexpected results.

The platform treated any invalid string as “Today’s Date”. Moving forward, for query reports that have filters enabled, a check was added whenever a user attempts to use an invalid filter in a date or date-time field. If a non-date or non-date-time string is used in this filter, then a “No data to display” message is shown to the user in the body of the query results table, and zero results are returned.

[Admin: To see other related posts, use the Date tag or Filter tag.]

Continue reading

How do you transform an unsupported date format?


We would like to upload a date in “dd.mm.yyyy” format. As long as TRIRIGA doesn’t support this format, what would be the best way to transform a string with “dd.mm.yyyy” to Epoch date, and then copy it to a Date field inside TRIRIGA? For example, advanced formula, custom task, etc.?

I think one of the possible ways is to leverage an ETL tool (e.g. Kettle Spoon) to transform data. See the Data Management (PDF) user guide.

[Admin: To see other related posts, use the ETL tag.]

Continue reading

Is there a way to get the proper date value for CBA?


Our workflow sends an outbound message by user action. For the Connector for Business Applications (CBA), the Connector user guide says:

For date values, the outbound query results include the raw values that are stored in the database and the formatted display values that are shown to the user. The displayValue node is added to the query results. The following example shows the default XML structure…

But for us, the outbound message has a different format… The <value> is presented in the same way as <displayValue> which is not acceptable because users may have a different date format. Is there a way to get the proper date value in <value> or use a single <displayValue> format for all users?

Continue reading