By default, the date-format is related to the chosen user language, the GUI starts up in. So for (US) English, the default format would be mm/dd/yyyy. It is possible to override this within the extended properties of the Runtime Configuration. Set the property customdatemask to dd-MM-yyyy for your required date format. [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/41874b27-7a9a-490f-8b70-557426d34569.png[/img] Within reports (for instance Crystal Reports) there are also settings to change the date format to any given format, but I usually prefer to let SQL server handle date formatting for me using the CONVERT function. For more information on the CONVERT function, please look at the Microsoft documentation: https://docs.microsoft.com/en-us/sql/t-sql/functions/cast-and-convert-transact-sql?view=sql-server-2017
This also applies when changing or adding a table/task/report/subroutine. Wouldn't it be possible to 'know' what objects need to be generated? When you want to assign a template to the changed objects, only the changed objects will (re-) generate (not the entire code-group)? Preferably this should be done while navigating to that screen, not while doing the update as it might slow things down. There is, in my opinion, no reason to present the user with a screen of out-of-date program objects.
[user=157]Hugo Nienhuis[/user] I wouldn't know. Perhaps someone with more knowledge about the inner workings of the reporting service can chime in? Looking a bit further at my current setup: I'd expect the logs to be created, provided the reporting service (user) has got the right authorisation to be able to write to the folder where the log files are written to. I think the location of the log-file can be set up in NLog.config. Also, the event-viewer should be able to provide additional information if the Reporting Service stops.
same :)
I usually have just one connection per reporting service instance running. Have you tried removing the first connection (temporarily) in order to see if it picks up the data from the second, 'test'? Also, is the service user authorised to access the database mentioned in the second connection?
SHOW TAGS! SHOW TAGS! :smiley: Why not make this a setting per developer? Just add a checkbox to the employee table within the SF and add a context context procedure showing the tag-tabs based on this setting. Make the default setting 'not-show-tags'.
Good to know, I was asked the same question today. Now I know the answer :)
Be aware that there are - at least for SQL Server - and depending on the version of SQL server you are using, quitte a few limitations when using in-memory tables. I do support using them, but thorrough regression testing is required when implementing them. Check here, for example: https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/transact-sql-constructs-not-supported-by-in-memory-oltp?view=sql-server-2017
Is 'none' the right name for this? I mean, the only purpouse is (I guess) starting a process flow. Why not call it what it is, something like 'Manual process flow execution'? Edit: Thinking about this, 'none' could also be used to retrieve additional information, where the fields can be filled from the default procedure. This saves space, by not needing a tab or even a complete form on a list of (read-only) information.
I think this should even be the default setting.
Why not remove the tasks/reports tab altogether? They are already visible in the main tab of the ribbon, when available?
Why do improvements need to happen via a ticket? Why cant we update the text ourselves? We all work at Thinkwise and (should be) knowing what we say, right? I assume this could save you guys a lot of hasstle and will get everyone that wants to get involved, directly involved.
Already have an account? Login
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.