Mixing
Are Custom Metadata Types considered External Data Sources?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
14
down vote
favorite
Back in 2016 we created a Custom Metadata Type with about 3000 rows. There is a trigger that reads all 3000 rows (via SOQL) and creates a map. This has been working for years, until Winter '19.
Now, when we run the test Class for our trigger (in winter '19), we get this error message:
System.QueryException: myCustom__mdt received too many records from the external data source
Summer '18 Orgs work just fine like they always have.
SO! When I try to debug that error message, I find this knowledge article.
Too many records received from external data source
This basically says:
When using an External data source configured to use Server Driven Pagination and for a query on an external object from this external source results in server responding with a result page size greater than 2000 records results in the below error - ...
SO! Are Custom Metadata Types treated like external data sources and the limit is only now being enforced in Winter '19? Is there a limit on CMTs that I am violating and can't find a reference to?
custom-metadata externalobjects
asked 3 hours ago
John Thompson
1,4621517
add a comment |Â
up vote
14
down vote
favorite
Back in 2016 we created a Custom Metadata Type with about 3000 rows. There is a trigger that reads all 3000 rows (via SOQL) and creates a map. This has been working for years, until Winter '19.
Now, when we run the test Class for our trigger (in winter '19), we get this error message:
System.QueryException: myCustom__mdt received too many records from the external data source
Summer '18 Orgs work just fine like they always have.
SO! When I try to debug that error message, I find this knowledge article.
Too many records received from external data source
This basically says:
When using an External data source configured to use Server Driven Pagination and for a query on an external object from this external source results in server responding with a result page size greater than 2000 records results in the below error - ...
SO! Are Custom Metadata Types treated like external data sources and the limit is only now being enforced in Winter '19? Is there a limit on CMTs that I am violating and can't find a reference to?
custom-metadata externalobjects
asked 3 hours ago
John Thompson
1,4621517
Whoa. That's crazy.
– Adrian Larson♦
3 hours ago
1
I opened a Case with SF Support... it's been escalated to the point where R&D is looking into it. I think it's a winter '19 bug. I hope it gets cleared up before release. I've been the little voice behind a known issue before, but never something like this!
– John Thompson
2 hours ago
2
Does it work if you query once with LIMIT 1500 and then another with OFFSET 1500 and merge them? Slapdash non-scalable solution but at least it gets you through the storm.
– Charles T
2 hours ago
@CharlesT I haven't tried it. A member of our Dev team was heading down that path while we awaited and answer from support. I might get some feedback on this tommorow. "Slapdash", I like that! I'm going to start using that term I learned from Charles T.
– John Thompson
40 mins ago
add a comment |Â
up vote
14
down vote
favorite
up vote
14
down vote
favorite
Back in 2016 we created a Custom Metadata Type with about 3000 rows. There is a trigger that reads all 3000 rows (via SOQL) and creates a map. This has been working for years, until Winter '19.
Now, when we run the test Class for our trigger (in winter '19), we get this error message:
System.QueryException: myCustom__mdt received too many records from the external data source
Summer '18 Orgs work just fine like they always have.
SO! When I try to debug that error message, I find this knowledge article.
Too many records received from external data source
This basically says:
When using an External data source configured to use Server Driven Pagination and for a query on an external object from this external source results in server responding with a result page size greater than 2000 records results in the below error - ...
SO! Are Custom Metadata Types treated like external data sources and the limit is only now being enforced in Winter '19? Is there a limit on CMTs that I am violating and can't find a reference to?
custom-metadata externalobjects
asked 3 hours ago
John Thompson
1,4621517
Back in 2016 we created a Custom Metadata Type with about 3000 rows. There is a trigger that reads all 3000 rows (via SOQL) and creates a map. This has been working for years, until Winter '19.
Now, when we run the test Class for our trigger (in winter '19), we get this error message:
System.QueryException: myCustom__mdt received too many records from the external data source
Summer '18 Orgs work just fine like they always have.
SO! When I try to debug that error message, I find this knowledge article.
Too many records received from external data source
This basically says:
When using an External data source configured to use Server Driven Pagination and for a query on an external object from this external source results in server responding with a result page size greater than 2000 records results in the below error - ...
SO! Are Custom Metadata Types treated like external data sources and the limit is only now being enforced in Winter '19? Is there a limit on CMTs that I am violating and can't find a reference to?
custom-metadata externalobjects
custom-metadata externalobjects
asked 3 hours ago
John Thompson
1,4621517
asked 3 hours ago
John Thompson
1,4621517
asked 3 hours ago
John Thompson
1,4621517
asked 3 hours ago
John Thompson
1,4621517
asked 3 hours ago
John Thompson
1,4621517
1,4621517
Whoa. That's crazy.
– Adrian Larson♦
3 hours ago
1
I opened a Case with SF Support... it's been escalated to the point where R&D is looking into it. I think it's a winter '19 bug. I hope it gets cleared up before release. I've been the little voice behind a known issue before, but never something like this!
– John Thompson
2 hours ago
2
Does it work if you query once with LIMIT 1500 and then another with OFFSET 1500 and merge them? Slapdash non-scalable solution but at least it gets you through the storm.
– Charles T
2 hours ago
@CharlesT I haven't tried it. A member of our Dev team was heading down that path while we awaited and answer from support. I might get some feedback on this tommorow. "Slapdash", I like that! I'm going to start using that term I learned from Charles T.
– John Thompson
40 mins ago
add a comment |Â
Whoa. That's crazy.
– Adrian Larson♦
3 hours ago
1
I opened a Case with SF Support... it's been escalated to the point where R&D is looking into it. I think it's a winter '19 bug. I hope it gets cleared up before release. I've been the little voice behind a known issue before, but never something like this!
– John Thompson
2 hours ago
2
Does it work if you query once with LIMIT 1500 and then another with OFFSET 1500 and merge them? Slapdash non-scalable solution but at least it gets you through the storm.
– Charles T
2 hours ago
@CharlesT I haven't tried it. A member of our Dev team was heading down that path while we awaited and answer from support. I might get some feedback on this tommorow. "Slapdash", I like that! I'm going to start using that term I learned from Charles T.
– John Thompson
40 mins ago
Whoa. That's crazy.
– Adrian Larson♦
3 hours ago
Whoa. That's crazy.
– Adrian Larson♦
3 hours ago
1
1
I opened a Case with SF Support... it's been escalated to the point where R&D is looking into it. I think it's a winter '19 bug. I hope it gets cleared up before release. I've been the little voice behind a known issue before, but never something like this!
– John Thompson
2 hours ago
I opened a Case with SF Support... it's been escalated to the point where R&D is looking into it. I think it's a winter '19 bug. I hope it gets cleared up before release. I've been the little voice behind a known issue before, but never something like this!
– John Thompson
2 hours ago
2
2
Does it work if you query once with LIMIT 1500 and then another with OFFSET 1500 and merge them? Slapdash non-scalable solution but at least it gets you through the storm.
– Charles T
2 hours ago
Does it work if you query once with LIMIT 1500 and then another with OFFSET 1500 and merge them? Slapdash non-scalable solution but at least it gets you through the storm.
– Charles T
2 hours ago
@CharlesT I haven't tried it. A member of our Dev team was heading down that path while we awaited and answer from support. I might get some feedback on this tommorow. "Slapdash", I like that! I'm going to start using that term I learned from Charles T.
– John Thompson
40 mins ago
@CharlesT I haven't tried it. A member of our Dev team was heading down that path while we awaited and answer from support. I might get some feedback on this tommorow. "Slapdash", I like that! I'm going to start using that term I learned from Charles T.
– John Thompson
40 mins ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
This is a Winter '19 bug. I've heard several other folks have the same issue and they put in tickets.
answered 2 hours ago
Mobot818
211
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
This is a Winter '19 bug. I've heard several other folks have the same issue and they put in tickets.
answered 2 hours ago
Mobot818
211
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
This is a Winter '19 bug. I've heard several other folks have the same issue and they put in tickets.
answered 2 hours ago
Mobot818
211
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
This is a Winter '19 bug. I've heard several other folks have the same issue and they put in tickets.
answered 2 hours ago
Mobot818
211
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is a Winter '19 bug. I've heard several other folks have the same issue and they put in tickets.
answered 2 hours ago
Mobot818
211
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
Mobot818
211
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
Mobot818
211
answered 2 hours ago
Mobot818
211
211
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Mobot818 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f233147%2fare-custom-metadata-types-considered-external-data-sources%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Whoa. That's crazy.
– Adrian Larson♦
3 hours ago
1
I opened a Case with SF Support... it's been escalated to the point where R&D is looking into it. I think it's a winter '19 bug. I hope it gets cleared up before release. I've been the little voice behind a known issue before, but never something like this!
– John Thompson
2 hours ago
2
Does it work if you query once with LIMIT 1500 and then another with OFFSET 1500 and merge them? Slapdash non-scalable solution but at least it gets you through the storm.
– Charles T
2 hours ago
@CharlesT I haven't tried it. A member of our Dev team was heading down that path while we awaited and answer from support. I might get some feedback on this tommorow. "Slapdash", I like that! I'm going to start using that term I learned from Charles T.
– John Thompson
40 mins ago