I see, that's a shame. Is upgrading to 2019.1 a possibility?
[quote=htimmermans][user=87]Tom van Druten[/user] I'm also curious whether this one copies lookup information as well (if not, that'll going to be a new wish).[/quote] Lookup information will require a reference, so nope :) (Though I do believe this could easily be added in the copy task)
Big. Fat. Yes. to this one. It's a shame you have to write defaults and such to only fill the current date when adding a row. Being able to set this as default value would be so much easier! AND a great addition to the 'Low - Code' principle.
The thing I don't understand is the fact it is such a technical name. Just name it 'Installer' or something you immediately recognize as the installer. Most people don't even know what a GUI is; Also twdeployer is an abbreviation for "Thinkwise Deployer". Also the config files have .exe in their name, while it isn't an .exe file. Looking at other software, I mostly see .config
Same for setting details to, for example, read-only in case no row is selected. Same for reports Same for add button in a detail, when no row is selected in the previous (main) document, which causes you not being able to add a row, because the PK/FK is not filled. Right now we have to write code for such things, while some simple bits on each table could fix this (and the GUI interpretating it). Would be a great value to our 'Low - Code' USP.
[user=30]Arjan Sollie[/user] . Before we sync a version to IAM we already made a new version for development in the SF. The version we'd like to sync has a project folder path which we alter from the DEV path to the PRODUCTION path. Now you don't have to worry about the replace path task in IAM. A huge problem with doing this in IAM is the fact you cannot see what is has been set to right now, so you have to query for example icon from tab in IAM. Another problem is: In our project all developers have more access rights on the file system, so if we simply forget to change the path after syncing we will see the icons, but the users won't. For us it helps a lot to just change the project folder path in the SF, before syncing.
I see. In our case the acceptation project folder is equal to the production folder.
Good idea!
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.