Return a list of EntityProxies when FunctionImport return type is a Collection#298
Open
Ixaruz wants to merge 1 commit intoSAP:masterfrom
Open
Return a list of EntityProxies when FunctionImport return type is a Collection#298Ixaruz wants to merge 1 commit intoSAP:masterfrom
Ixaruz wants to merge 1 commit intoSAP:masterfrom
Conversation
|
|
Ixaruz
force-pushed
the
PythonListFromCollectionInFunctionImport
branch
from
7d183de to
3d5ea27
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What the title says.
I had to rename the
EntitySetof theFunctionImportin the test metadata.xml to not include the namespace, or else the constructor ofEntityProxywould be unable to find the right entity set...since the
EntitySetin theFunctionImportofget_maxalso was just"TemperatureMeasurements"(not"EXAMPLE_SRV.TemperatureMeasurements"), I assume it was just an oversight in the xml (as it wasn't tested before).I don't know if my "fix" approach is too short sighted, I just wanted to provide potential fixes, as we needed them in our production.