Skip to main content
Question

Substitute Variable in scheduled database taks


Forum|alt.badge.img+9
  • Sidekick (Customer)
  • 80 replies

Hi all,

 

I previously had a topic on this, which lead to looking into the NLS settings, but unfortunately not found a solution yet. So hope someone has some valueable input for this.

We have a scheduled database task for the Supplier Payment Proposals, in which we use a “substitute variable”, being Start of Next week. However, the created Proposal, has start of next week as Sunday, and not as Monday.

When i manually create a Supplier Payment Proposal, it does take Monday as the First Day of Next Week. 


 

 

We have changed the NLS Setting for the Database Processes to Danish, set the Database Settings to Danish as well as the Server settings. But nothing seems to have any impact on the scheduled database tasks behaviour.

2 replies

Forum|alt.badge.img+3
  • Do Gooder (Customer)
  • 8 replies
  • March 21, 2025

We also have the same problem. Anyone that managed to solve this? 


sdhalk
Do Gooder (Employee)
Forum|alt.badge.img+4
  • Do Gooder (Employee)
  • 11 replies
  • April 25, 2025

Hi ​@Arend, ​@lnilsson,

In Reports, CSV values are resolved by the server. The server-side implementation does respect NLS_TERRITORY, which affects the first day of the week.

However, NLS_TERRITORY is set based on the user's language. When the language is changed, NLS_TERRITORY is changed to match the region of that language (per session). This, in return, will change the first day of the week.

For example, if you are in Sweden, you should change your client language to Swedish in order to adjust start and end days according to the regional settings.

These settings cannot be decoupled. At the current stage of IEE support, this behavior will not be modified, as it will require major changes that would impact other parts of the application as well. This will also go beyond a client implementation, as server-side changes will be required as well.

This is considered as a framework limitation.

Hence the workaround for the current issue would be to change the application language to Danish to get the date according to the region Denmark.

I hope this information is helpful.

Thanks,

Sarasi


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings