Hi Svetlana,
we encountered the same problem with the Git integration.
We don't understand why the expected behavior is a "replace" instead of an "add". This also does not correspond to our understanding of Git.
The button in the PAW "Add new objects" is also misleading.
Let's take a simple example:
I have created a new TI process in PAW and want to add it to my repository. There is no way to add only this process, because otherwise all other objects in the repository will be deleted. I always have to select all objects that are already in the repository. We have customers with large TM1 instances. I can't add all objects there every time.
We would like to use the integration for version management and, for example, to transport objects between DEV-Test-Prod instances. Unfortunately, this is not possible with the current functionality.
Can you please explain what your understanding is and how you recommend using the Git integration?
Many thanks and best regards
Tim
------------------------------
Tim Geilen
Senior BI Consultant - Braincourt GmbH
------------------------------
Original Message:
Sent: Fri January 26, 2024 05:09 PM
From: Svetlana Pestsova
Subject: Repository Integration behaving differently
Hi Dean,
Yes, the "replace" behavior is expected.
A new Git commit will appear as a replacement if the content in the new commit is unrelated to the content in the specified branch. In other words, the server does not do incremental change to the existing branch. Instead, it always create a new commit.
If the new commit contains some changes to the object in the old branch, the object will appear to have been changed. If the object is not in the new commit, it will appear to have been deleted.
Best regards,
------------------------------
Svetlana Pestsova
IBM Planning Analytics Product Manager
Original Message:
Sent: Fri January 26, 2024 04:21 PM
From: Dean Watts
Subject: Repository Integration behaving differently
Svetlana,
So to confirm, when a user selects 'Add objects to repository' and selects an Existing branch, this REPLACES all contents of that branch. If items previously in the branch are not reselected, they will be removed.
Dean
------------------------------
Dean Watts
Original Message:
Sent: Fri January 26, 2024 02:09 PM
From: Svetlana Pestsova
Subject: Repository Integration behaving differently
Hi Dean and Bilal!
Thank you for verification.
It's always been like that, a user needs to select all objects that are needed to be pushed.
Best regards,
------------------------------
Svetlana Pestsova
IBM Planning Analytics Product Manager
Original Message:
Sent: Fri January 26, 2024 11:47 AM
From: Bilal KACEL
Subject: Repository Integration behaving differently
Hi @Dean Watts and @Svetlana Pestsova,
This is what I tested:
Step 1: Pushing objects from the PA instance to a B1 branch in GitHub
Step 2: From the same instance, push new objects (not present in step 1) to the same B1 branch created in step 1.
Observation: in GitHub, the objects pushed in step 1 (if different from those in step 2) disappear. Only the objects pushed in step 2 are found.
I don't know if the behaviour is different from before.
Regards,
------------------------------
Bilal KACEL
Original Message:
Sent: Wed January 24, 2024 09:47 AM
From: Dean Watts
Subject: Repository Integration behaving differently
Community,
We seem to be experiencing a different behavior to the repository integration function within PAW with 2.0.92. Previously we could create a new branch, add items and then later come back and add more items to that now existing branch. Now when we create a new branch and add items, when we come back to add more objects the branch is getting overwritten with just the new. All existing objects are being deleted. Is anyone else seeing anything similar? Is there a new configuration that needs to be performed?
Thanks,
------------------------------
D Watts
------------------------------