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

Insights: "roas is not valid for fields param" #88

Closed
cscanlin opened this issue Aug 26, 2015 · 5 comments
Closed

Insights: "roas is not valid for fields param" #88

cscanlin opened this issue Aug 26, 2015 · 5 comments

Comments

@cscanlin
Copy link
Contributor

This bug was validated in the Ads API v2.4 Q&A:
https://www.facebook.com/events/873155332753388/878318465570408/

Reposting this here for better issue tracking

@rituparnamukherjee
Copy link
Contributor

This is fixed in the latest version.

@cscanlin
Copy link
Contributor Author

Just to clarify, "fixed" really means "removed" in this case, correct?

@rituparnamukherjee
Copy link
Contributor

Yes, that is correct.

@cscanlin
Copy link
Contributor Author

Is there any chance this will be added back in a future update? This functionality would save a few dozen lines of code from by program, especially if it could be used in the filter parameter.

@rituparnamukherjee
Copy link
Contributor

It is hard to say at this point if the field will be made available again in later versions.

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

2 participants