-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
[Improvement] Forcing a Metadata update #1256
Comments
But it's hard (impossible?) to refresh it for only one tool... The cache is general for the XTB, not for a tool. |
There is a feature to use a global metadata cache for a connection but not all tools are using this. And if they don't, then they are handling metadata on their own way. |
I like that idea too. |
I've been testing a bit and now committed in FXB #897, and I think it just works, by calling the ConnectionDetail.UpdateMetadataCache(true) Anyone want to test? |
@rappen |
Either build the latest repo, or get the DLL from here: XrmToolBox/Beta |
I just tested and noticed a different behaviour based on the value of "Use cached metadata in XrmToolBox". If the "Use cached metadata in XrmToolBox" is unchecked, everything is working as expected. The newly created column appears immediately after "Reload all metadata" But if the "Use cached metadata in XrmToolBox" is checked, the newly created column does not appear in the list when I click the "Reload all metadata" for the first time. (Maybe the cached metadata is being retrieved in the background). I waited for a few minutes (in case there is any background process which updates the metadata once the retrieval is completed) but the new column did not appear. It finally appears when I click "Reload all metadata" for the second time. In summary, "Reload all metadata" needs to be clicked twice to see the updated metadata if the "Use cached metadata in XrmToolBox" is checked |
I've seen the exact same problem... no idea why. |
|
It should be done that way... but I'm not sure why/how I made it wrong... So if the user wants to force reloading, it does this before getting the metadata:
This is always done in milliseconds. So it isn't really loading all metadata. But it works, if done twice. I know I ain't best at threads/task/await things... |
Looks like you’re missing a |
Did I say I'm bad at tasks? I was looking at other calls like this, and first I had New version to test it here: XrmToolBox/Beta |
It would be nice to have the possibility to force a Metadata update without the need of closing the XrmToolBox (XTB).
Example Scenario:
I open the XTB and create some queries using Fetch XML Builder (FXB). While XTB is still open I create a new table or a column on an existing table. To be able to use the newly created table/column I have to close the XTB and reopen it so that the Metadata is updated. This costs time especially because I might have to recreate all queries.
I also created the same issue in the FXB Repo
rappen/FetchXMLBuilder#897
The text was updated successfully, but these errors were encountered: