Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Activation of XSLT objects fails on first import #69

Open
WegnerDan opened this issue Mar 20, 2021 · 3 comments
Open

Activation of XSLT objects fails on first import #69

WegnerDan opened this issue Mar 20, 2021 · 3 comments

Comments

@WegnerDan
Copy link

WegnerDan commented Mar 20, 2021

I've installed this repo in several systems over the last few weeks and every time I've had to manually activate XSLT objects after import. After manually activating, everything works fine. I'm not sure if this is a known abapGit issue or if I should have opened this at the abapGit repo.

This is what it looks like after first import:

grafik

@frankbrandt
Copy link

I was experiencing the exact same issue. However, I was able to activate the transformations within ADT and it looks fine in abapGit afterwards.

@WegnerDan
Copy link
Author

As I said, manually activating works fine, but I think this should be done automatically in abapGit.

@mbtools
Copy link
Member

mbtools commented Jan 20, 2022

This is not an abapGit issue but an SAP bug:

2859159 - XSLT: Support dependencies on inactive objects
https://launchpad.support.sap.com/#/notes/2859159

(See also abapGit/abapGit#5262)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants