rappen
commented
4 months ago Thanks @FredJoly, for your suggestion!
My guess is your traces don't include similar xyz new_tablename {45756b6d-a787-ee11-8179-002248a071f6} bla bla, where finding records needs to find the entity name "near" the guid.
Would it be possible to share some examples from your logs? If too sensitive, can you email me instead?
Any chance you could add a kind of whitelist to allow the tool to search custom entities? Our dynamics environment is heavily customized, and mostly avoids using OOTB functionality for various reasons. We have probably close to 300 custom entities.
In this case, I use the tool extensively to debug a set of workflows that operate on a set of about 4-5 custom entities (and the contact entity). Being able to tell the tool "hey, please check these 4-5 entities) would make this feature useful. Otherwise, as it stands, this feature is useless to me at the moment because it's not searching the correct tables. If it was, it could potentially save me a lot of logging, which would reduce the chance of exceeding the log limit.
Originally posted by @FredJoly in https://github.com/rappen/PluginTraceViewer/issues/193#issuecomment-2203225712