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

Executing multiple services #70

Open
emilekukkuk opened this issue Jun 22, 2017 · 8 comments
Open

Executing multiple services #70

emilekukkuk opened this issue Jun 22, 2017 · 8 comments
Assignees

Comments

@emilekukkuk
Copy link

I have an issue where I need to extract data from two different URL's for the same company.

Calling a new service, sending the service name and executing the query works fine for the first URL.

When running a second one ( With a new URL ), the execute method tries to retrieve the data still from the first URL, although the field names are now different in the 2nd one.

/usr/local/rvm/gems/ruby-2.4.0/gems/ruby_odata-0.1.0/lib/ruby_odata/service.rb:376:in block in entry_to_class': undefined method INSite_Formulaa0129565ae50e71181a00aec8e401db6=' for #NSco:0x000000033b0cd8 (NoMethodError)

I suspect it's to do with the dynamic creation of the instance variables via the instance_variable_names method.

When checking the edmx for both, they are indeed different.

Any suggestions to get this working?
Thanks.

@visoft visoft self-assigned this Jun 22, 2017
@visoft
Copy link
Owner

visoft commented Jun 22, 2017

Thanks for reporting this bug. I'll check it out today.

@emilekukkuk
Copy link
Author

Thank you very much!

@visoft
Copy link
Owner

visoft commented Jun 25, 2017

@emilekukkuk Does this happen with the current version in the develop branch?

visoft added a commit that referenced this issue Aug 5, 2017
@visoft
Copy link
Owner

visoft commented Aug 5, 2017

I checked in a spec for this in the develop branch.

@emilekukkuk
Copy link
Author

Thank you so much. Sorry I haven't checked in a for while. Was in a hurry and used another component.

I'll see if I can test the new commit.

@karolkulesza
Copy link

Is this fixed in any of the versions > 0.1.0 ?

@visoft
Copy link
Owner

visoft commented Aug 21, 2020

@karolkulesza - Check the develop branch out, it should have changes for this

@karolkulesza
Copy link

@visoft : Thanks for the feedback.

Unfortunately, using the latest version from develop I have the same issue, still.

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

No branches or pull requests

3 participants