forcedotcom
error when page layouts to work item
Describe the bug
To Reproduce Steps to reproduce the behaviour:
- add page layouts to work item
- commit
- see errors
@TheMixDevOps I've tried to reproduce this with some simple examples and haven't been able to. Is there anything more you can tell us about your environment/situation? Do you have any Layouts that commit successfully? Do other metadata types commit successfully?
@TheMixDevOps We do have a known issue related to pull Layouts with special characters in the name. Do you happen to have special characters in the name? Space should be okay, but other characters like : or others are known to be an issue currently. We do have a fix for that coming in an upcoming patch release.
I checked names of the page layouts via SF setup object manager and I found out there is extra space character after the name, i.e 'Footer social media links ' Because I already deployed changes including these two pages (even with extra spaces at the end of the name) via change sets, I will not need to use DevOps to progress the work item any further. I can work on assumption that the extra space character might have caused the issue. What do you suggest I can do now? Should I just keep the work item there as is or do some additional action with it?
@TheMixDevOps I actually don't think the spaces, even trailing, should be a problem. At least I can't reproduce it in a simple test here. Is that metadata namespaced?
I've run into this issue. We have some page layouts with "." in them, and when pulling them manually it comes through with the special character markup like $e. or something like that. Then we get this error when trying to commit or promote. If we pull the layout change through from source tracking specifically it works, but not manual components
