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
Unsupported Object types #138
Comments
Hi, Authorization objects and classes are supported, however AUTH = "Authorization Check Fields" are not supported. Also no serialization for workflow objects have been implemented. If you have the time, feel free to implement support for the objects you need and submit a pull request 😄 see examples in LCL_OBJECT_* classes. If you just need some of the objects exported, just comment out the error handling in ZABAPGIT(or make a copy of the program) and have it ignore the non-supported object types. It will also work if you restructure the your project into multiple packages, but I dont think this should be done just because of abapGit. |
AUTH support added, |
Hi, thanks for adding AUTH support. I was able to export my package now, but I had to comment out the following object types: One hint for PDWS, there is an existing functionality by SAP to export Workflows. For PDTS, I don't know. Unfortunately, I do not have time because of work and personal life constraints, even though I would love to participate in your great project. Thanks for everything! |
hi, I've added the objects to the list, and created separate issues #151 #152 #153 #154 #155 #156 for each of the types, perhaps someday someone will implement support 😄 I'll close the issue, each object type can be tracked in the above issues. Feel free to create a new issue if you run into problems or have questions |
Hi,
maybe this is not an issue and I am just too new to this.
I just installed ABAPGIT on our NW 7.40 machine.
I linked one of my big workflow projects including lots of objects of different kinds as an offline project. When I try to export it I get the error message "Object type AUTH not supported, serialize". I suppose authorization objects are not supported because they are not ABAP code. Am I correct in assuming that Workflows and standard tasks are also not supported?
Is there any fix for that or do I need to restructure my project into sub-projects so that all ABAP code is in one sub-project and only this sub-project is linked to ABAPGIT.
Could you provide a list of objects which are allowed and serializeable by ABAPGIT? Maybe it already exists out there and I just missed it :/
Keep up the good work and thanks a lot!
Cheers,
Jani
The text was updated successfully, but these errors were encountered: