I had used a mapping to get out of an issue of querying within trigger.new, and when I tested a few times doing a "Mass Order" functionality (where orders are made for a mass number of accounts), it went through, no errors. I went to test it again, and I got an error of 101 queries.
This trigger fires before and after insert, and before update. In none of these conditions (ie. in no trigger.isUpdate condition etc.) is the query that's putting it over the limit. It's a query for the Pricebook...
pbList = [Select ID From Pricebook2 Where IsActive = true AND IsStandard = true];
... and I'm guessing that even though it's not in trigger.new, it's just going over because this is inserting SO many orders. This seems like a very necessary thing and I'm wondering, what is my alternative to this query other than hard-coding in the ID? As mentioned, the only errors I'd gotten before was querying account info in Trigger.new, and when I changed it to a mapping implementation, this functionality did work fine. It does make sense that this would come up, though. What are my options?