It's the same i got and it's why i opened this thread. The reply as you can see, it's "it is by design and it's not a bug". I guess this issue was not fully understood, because it makes totally unuseful the combination property value/builds/syncronization system. You've to set the property value manually per build and syncronize in the same way. How can it considered a "no bug" it's incomprehensible: it's an evident bug. But fortunally, i'm not the only one i got it, and i guess there are a lot of users they can tell the same, out there.Julian758 wrote: ↑Fri Dec 15, 2023 7:47 amHello, I recently updated to version 21.2.2, and I've encountered a significant issue with the Property Variable System, specifically regarding synchronization with the source path. It seems that the property variables do not update internally when I change the associated build configuration. Despite visually reflecting the changes in the property window, the internal value remains fixed at the initial configuration, even after performing a refresh in the files and folders section. This discrepancy becomes apparent during the build process, as the running log output displays information that is not aligned with the newly set property path variables. It would be greatly appreciated if this synchronization issue could be addressed.
Liviu wrote: ↑Fri Dec 22, 2023 2:11 pmHello guys,
Sorry for the delayed reply on this. Recently we have had many more support tickets than usual.
I have a hard time reproducing this problem.
To shorten the investigation time, if you can, please send us your .AIP (project setup) file by email to support at advancedinstaller dot com along with step-by-step test case that we can follow to reproduce this problem.
We apologize for any inconvenience you've experienced and we are committed to delivering a solution that meets your expectations.
I've been able to reproduce this behavior. This seems to be the intended behavior, as my colleague Catalin previously mentioned.In brief: use properties path values with several build configurations; setting them to different path value; switch by them and go to files and folder section, convert to source path a specific folder files; select a build and try to build the project and you will see the previous path is still them and the internal variable related to property path value is not update although you set a specific property path value in "properties" section, associated with a specific preconfigured build.
Please note that the Organization page does not have a dedicated option for switching builds, as this is not supported. The AI_BUILD_NAME is not automatically updated based on the selected build."AI_BUILD_NAME" variable does not reflect the current build name is building: When i launch the setup and install the files, i find the directory/component it would be excluded instead. This is sympton that AI_BUILD_NAME it's not aligned with current build name configuration i've set to build the project. Using CLI is the same.
AI_BUILD_NAME is a default project property, so not user-defined; when i try to specify in conditions settings it shows me the several build names i've in the project. It's a property available in those ones used to specify the conditions in several parts where them are available. So, if this property does not reflect the build name which i'm building the project for, what is its purpose and where and when it's updated ? I'm not able to find a sense of using this property, staying what you're saying, as the Organization section allows to specify a condition for a specific component where there are available all the project property in which i could check its value. What is the design it about so ?Liviu wrote: ↑Wed Jan 03, 2024 2:36 pm
Please note that the Organization page does not have a dedicated option for switching builds, as this is not supported. The AI_BUILD_NAME is not automatically updated based on the selected build.
Once you have add the desired condition on the condition field, this condition should not be changed by us.
I've tested your configuration. As i told before, i confirm it works with files only. If the condition is applied to a whole folder, it does not work. It could be resolved using "Condition Files" on right click on a folder; but it's a bit misleading as one could expect it works to an entire folder too. I will send you my .aip for a check so you can give me some tips it about.Liviu wrote: ↑Tue Jan 09, 2024 4:22 pmHello,
According to your screenshot, all files added to the GRPC folder should only be installed by the MINISTEROINTERNO setup build.
I've tested this and it worked as expected for me.
For example, the msi.txt file is installed only by the MSI package built from DefaultBuild. This msi.txt file is not included in the other build I have. This works as expected.
Please send us your .AIP project file by email to support at advancedinstaller dot com so we can review its settings. Also send details of expected behaviour. For example, I want "file1, file2" to be included only in the MINISTEROINTERNO build.