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

"Failed to match structure * with a structure from rps" when using an alias reference. #358

Open
tscaff opened this issue Jan 18, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@tscaff
Copy link

tscaff commented Jan 18, 2024

When attempting to use an assigned alias name in the Synergy/DE Repository, I noticed that the following errors started occurring in my Harmony Core Regen attempt.

harmonycore regen
SolutionDir '' is not set. Using the current working directory.
Scanning '..\WebApi' for HarmonyCore project files
Using MSBuild from path: C:\Program Files\dotnet\sdk\6.0.418

Failed to match structure ACCOUNTSTATEMENTS with a structure from rps
*** Files that look like they need to be deleted/removed from projects ***

Here is the repository schema entry

Structure CIFPROFILESTATEMENTS ASCII Modified 20240118152751
Description "GridProfileStatements response"
...
...
...
Alias ACCOUNTSTATEMENTS Structure CIFPROFILESTATEMENTS

This is a portion of our ~library.dbl entry that we are building the SMC from

{xfMethod(intWeblib, elbmacro, name="subroutineMethod")}
;;;


;;;Return account listing matching filter data
;;;

.subroutine subroutineMethodHome

{xfParameter(name="response", typeCol, structure="AccountStatements", dataTable=false)}
out required a_returnData ,@Arraylist

.proc

Are repository aliases not supported?

@tscaff tscaff added the bug Something isn't working label Jan 18, 2024
@hippiehunter
Copy link
Contributor

I checked with Steve and it doesnt seem like we have any support for using a structure alias in xfParameter like that. Is this a significant issue for you?

@tscaff
Copy link
Author

tscaff commented Jan 19, 2024

Hi Jeff, it's not a super significant issue at the moment

We were just excited about using it...so it was just unexpected when it didn't generate the aliased structure.

We have a workaround for now.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants