Hi Boudewijn,in the meanwhile I created a TCP ticket and after also sharing my SF-DB with Thinkwise, they decided it is not an issue on our SF as Thinkwise technicians are not able to reproduce it on our uploaded SF.For us this is really strange as you are nr 3 mentioning the issue.We tested it about 10 times this upgrade and everytime the issue occurs.Now agreed with Thinikwise support to just run the DELETE-statement mentioned by @PatrickW as these records are not needed anymore.So in our opinion there is something missing in the cleaning part of the upgrade script, but for some reason no error-message is triggered, and it doesn't occur in all situations….strange…..
very looking forward to this request!Isn’t it as simple as just additionally adding column “task_variant_id” to PK of table “tab_task” ?(as this is the error I get when trying to add a variant of a task to the same table)Thanks
Hi @René W , can you please explain how you were able to create the hyperlink in the message ?For some reason my A HREF is just interpreted as text and now converted to an hyperlink 🤔Currently using:DECLARE @url NVARCHAR(MAX);SET @url = CONCAT('<text>' ,'<a href="https://www.nu.nl" target="_blank">MyLink</a>' ,'</text>')EXEC tsf_send_message 'URLtest', @url, 0;Created message:Thanks
Hi Mark,thanks for your reply on this.I think developers will be ‘noticed’ that the default setting is in place for custom configurations or that the custom configuration has a different setting compared to default. In that last situation the value is ‘bold’. But, my issue is regarding the fact that if de default is set to value 1 and the custom configuration is set to 2. When running both configurations then, they both have the extended value set to 1.
hi Mark,adjusted your query slightly and hereby the results.So the value is correctly stored in the DB.Maybe this is telling us something: 🤔Detail info for the red crosses is:“An item with the same key has already been added.”
TCP ticket created accordingly and reference to this topic added.Thanks.
I also found this in our Docs: https://office.thinkwisesoftware.com/docs/docs/sf/resource_scheduler.html This should make sure you get a great functioning Calendar. new link: https://docs.thinkwisesoftware.com/docs/sf/resource_scheduler
maybe to elaborate some more on the question a screenshot from the view displayed in the Thinkwise end application, and displaying the same data in the cube.The cube uses the same view as a datasource.The view has a layout specified with the follwoing code:-- Only allow updates on FORECAST-dataIF @QuantityType <> 'FORECAST'BEGIN SET @Quantity_type = 1ENDView:“Order”-records are not updatable which is correct. Cube:For the same record (and Order-record), it is possible to update the value, which isn't correct.Hope someone has the answer for solving this issue.Thanks
hi Anne,thanks for your workaround.Was also already thinking about it but as you mentioned this not a real solution.Also the details are now duplicated...(but maybe I also find a workaround for this like prefiltering the details screen - if possible)Will also create an Idea to support the layout functionality also for the cube-component.
Already have an account? Login
Enter your 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.