Hi @MiLeNL, I talked about it on the Community, I also encountered the concern here : Regards, Théo Thanks @TheoB , not the answer i was hoping but at least it's clear it does not work.
Hi Malan. Yes, it seems it available from 22R1. Searched for Projection Action in documentation for track 21R2 and didn’t find anything. Best regards. Gonzalo. Hi Gonzalo, Just tried to do this for ‘PartNo’ on the window ‘Part’ or ‘Inventory Part’, even though it is part of the Default call no value is given. When doing it for the field ‘Description’ it does work… Is this not possible for Key values? Regards,Mitchel
You can remove it by using the Right Mouse Button in the Custom Fields window header you have open. Use the cleanup function.
It does not really sound like a good idea to abuse an IAL schedule for a trigger to send out mails regarding projects. Why don't you use a migration job with the method command_sys.mail. You can use your select statement (SELECT * FROM ifsinfo.BAD_PROJECT_SPEND_LAST_WK) as input for the migration job. Can simply schedule on a weekly basis.If you want to use this approach;Guessing it triggers multiple times due to the IAL object getting status updates from the background job which updates the IAL. e.g. When the IAL updates it will get the state ‘Updating’ when finished it goes to another state. Probably if you add ROWVERSION to your mail output you will notice you will get 2 different rowversions.
No native solution i have found. The customer requirement ended up going away but i planned either to write a custom projection to make use of the doc man number counter, or write my own solution outside of IFS and use that. Shame really as number counter seems really close for wider use, but its missing just a bit of functionality. I just thought of the same this morning 😀. Created a Custom Entity with ID1 and ID2, the Next Value function and a Custom Projection on top of it. Every time you make an API call to Projection, you will get the next value. More is not required at the moment. Indeed a shame it's not a standard function in the standard number counters projection.
If you just want to change the logo, you don't need to make any report adjustment (assuming you are on cloud). Place the image you want in the ‘Report Images’ on the Logos tab.https://docs.ifs.com/techdocs/22r1/050_reporting/251_operational_reporting/210_report_images/ Go to Company and find the field Document Logotype. Give in the exact name of the image you just uploaded. It should now start to appear on the report layouts.
Hello I'm having a bit of task to try and make use of oracle sequences in IFS Cloud and stumbled upon number counters: The solution proposed in that topic looks to be what I'm after, however I'm having trouble finding a way to specifically generate a value from a projection function. The solution detailed is very much reliant on database access, but with IFS Cloud we have to assume no DB access. So i am looking for a projection that in essence calls ‘next_val()’ and returns the next value of the counter/sequence. Is there one? I got the exact same requirement. Did you ever find any solution?
It seems to me as if your input file is using a different delimiter as what you gave in your migration job. e.g. the error message is telling company ‘;EXEMPT’. This does not look like a company, but the value for field ‘TAX_LIABILITY’. Also seems like the delimiter is ';’. Did you set the correct delimiter in the Formatting tab?
Basically you can execute any procedure from the Migration Job. So what you did should be possible. However you do need to map the right keys into the remove procedure. e.g. it's asking for OBJID, OBJVERSION and ACTION (Action is ‘DO’). But they are not mapped. Both Source Column and Default value are empty. If you map the columns i think it should work.
-- Same answer already given 😀
State is one of the few fields which get translated in runtime. Normal data fields do not, as you are typing them in manually.
OBJSTATE is the actual database value which always remains the same.STATE is a translated value which depends on the language of the user.e.g. OBJSTATE = ‘Closed’ STATE when logged in in English is ‘Closed’ STATE when logged in in Dutch is ‘Gesloten’ STATE when logged in in German is ‘Geschlossen’ If you only use 1 language in IFS it does not make a difference 😉.
If you use Aurena, you need to use the Aurena URL. Also note that you have two element and lobby types; Enterprise Explorer or Aurena. The following documentation should be useful.https://docs.ifs.com/techdocs/22r1/040_tailoring/250_lobby_configurations/080_navigation/ Bonus tip; if you want the filter to be language independent. It's better to use OBJSTATE. As State is a translated value.
Thanks Anmise, Is it possible to update this? Per ISO8601, first day is the week is Monday. Arend Where are you using it? In the client I believe it’s converted to match your browser locale e.g. if I’m searching with my browser set to Denmark, and I use #NEXT_WEEK# I will get (Created ge 2022-11-28T00:00:00Z and Created le 2022-12-04T23:59:59Z) If I change it to US, then I get (Created ge 2022-11-27T00:00:00Z and Created le 2022-12-03T23:59:59Z) Didn't know so just tested by practical example 😉. You are correct! Also makes sense as they are Context variables so they take into account the….. context.
In the data source, make sure you format the data as a currency. In the element design, format the column to be printed italic.
You can use the report rule action to select a printer.
Seems like it's triggered by some form of routing rule. Not sure about the error…. Might be setup of IFS Connect which is not correct. Can't help out in that one.
Seems your rule fires… so that probably means an application message has been posted to push out an e-mail. That might be hanging somewhere. See if you can find any application message.
Yup that's it. Are you pressing ‘OK’ after the print dialog has appeared? Typically the report rule log should show a log entry with like ‘No condition met’ or something like that if you print. To troubleshoot i would suggest to remove the condition and make sure it fires without any condition attached to it.
Note that report rules only fire when ‘OK’ is pressed in the print dialog.Things you can checkEnable Report Rule Logging in the system parameters and check in the report rule logs if the rule triggers. If it triggers, check the application messages if a message is created to send out a mail. Check if the application message is not in failed state.
Think what you are after is a CASE statementSELECT CASE WHEN ‘Value’ = ‘Condition’ THEN ‘Outcome’ ENDFROM VIEW e.g.SELECT CASE WHEN param_id = ‘A050-H’ THEN ‘103’ ENDFROM CUSTOMER You can extend a case statement with multiple conditions. Also escape it with ‘ELSE’ CASEWHEN… THEN ..WHEN... THEN ..ELSE …END
Thanks, but it still isn’t working. No errors, but not rows are exported either. Don't forget to give the columns positions in the ‘File Mapping’ tab. In the ‘Rules’ you can also enable a file header to export column names.
I don't get it, might be i'm getting it wrong.You create a Quick Report. Once created (e.g. Saved) you have two options→ Press Publish. This will grant it to all permission sets as mentioned in the Documentation.→ Grant the Quick Report Projection to only certain permission sets. Note that the ‘Publish’ button does not need to be pressed in order for the Quick Report to be usable. Think the issue might be with the word ‘Publish’ instead of for example ‘Grant all’.
Don't think you can auto-populate. The way to do this would be to create an event which does something if the new state is ‘Closed’ and fetches the Logged in User. You can use the variables which are attached to the event. Then insert/update the value into the Custom Field.
Think your source/file mapping tabs are empty or none of the columns are mapped (e.g. all pos are '0’).
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.
