I’ve used the Query Designer to create a projection query that includes a date field. I’ve added a filter parameter for that field, since I want the date applied to the filter to be dynamic. The documentation says I should be able to use a context substitution variable in the datasource designer with that parameter.However, when I use #TODAY# as the parameter value on the datasource, I can see that the substitution is adding single quotes around the date value, producing a datatype mismatch error. The request header shows the URL looks like this:/main/ifsapplications/projection/v1/QueryProjectionReliability_Monitor_Due_Count_By_Assembly.svc/GetReliability_Monitor_Due_Count_By_Assembly(CurrentDate='2023-11-07')?$select=AssemblyTypeCode,CountOfMonitorDue&$orderby=AssemblyTypeCode&$top=25&$skip=0Note the single quotes added to 2023-11-07, turning it into a string value. If I manually remove the single quotes, the URL returns the expected payload.How do I keep the #TODAY# CSV f
It appears that with 21R2, there are only 5 Lobby Element background colors available (if you include white as a color), and 1 Accent color that can be defined in the Appearance Designer. Is this correct? While no colors could be user-defined in 21R1, there were 18 options provided, making it easy to group common lobby elements by color.In the case of the pre-defined colors, white is a poor choice, and the other 4 are both commonly used indicator colors (red, yellow, green, etc.) and are such a low saturation as to make it difficult to see them against the default background color.Am I missing the ability to change Lobby Element background colors elsewhere, or to add additional colors to the available palette?If this is by design, what is the use case for this?
Does anyone know if there was a change made from 21R1 to 21R2 in regards to Lobby Element Datasources, and how the system validates the views when creating a new datasource? We have a number of non-standard views that we use to demo, since there are minimal out of the box elements created for the Aviation Maintenance solution at this time. Any datasources that already existed when the environment was migrated continue to work. If I export a datasource from 21R1 and import it into 21R2, it works. If I edit an existing datasource that uses a not-out-of-the-box view, I can click on View Columns, and I get to see all the columns. But, if I try to create a new datasource and use one of those non-standard views, as soon as I take cursor focus off of the view name field, a toast message appears saying the view can't be found, and I cannot proceed.
I have a lobby element that counts overdue items. There is currently no “Overdue” indicator on the record, rather the count is based on a due date being less than today.On the page, you can filter a date/time column using #TODAY# (or other similar options) but that value gets converted in the URL to a literal string (2022-01-12T00:00:00Z for example).When setting the navigation URL for the Lobby Element, I’m trying to pass a querystring value that will filter the page results appropriately. How can I do this? Using something like ;$filter=DateToFilterOn lt #TODAY# just throws an error.Below is a screenshot of the page filtered manually, and the (cleaned up) querystring for the page, showing #YESTERDAY# converted to a literal value.;$filter=Objstate eq IfsApp.CroExchangesHandling.CroExchangeLineState'InExchange' and Contract eq '90' and PlannedReceiptDate le 2022-01-12T00:00:00Z How can I link from a Lobby Element to a page, and have the page filter a date column using a relative date
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
