This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Batch-recalculate property for all objects in a vault

Hi,
Apologies if this is obvious somewhere, but I've looked, honest! Simple question: How can I automatically recalculate an automatically calculated property for all objects in the vault? I've already locked myself out of a couple of sandbox vaults trying to get this to work.

A bit more detail: The properties involved use a vbscript with an SQL query in it to get component data from an external database. One update a day is fine. But how?

Seems like this might be a bit buggy:
https://community.m-files.com/index.php?topic=11850.msg32810#msg32810
https://community.m-files.com/index.php?topic=6072.msg32806#msg32806

Is there a better way?

Thanks

Matt
Parents
  • Sorry, I should have put in a bit more context.

    We're using M-Files to manage our mechanical CAD files (3D models and drawings, basically, with a few other hangers-on). I'm trying to set things up as a "one stop shop" for our designers, to save us from having to rummage through the ERP system (which like all ERP systems is extremely user unfriendly), so I want to include on the metadata sheet things like how many of a component we have in stock, how quickly we burn through stock, how much it is, where to find it in Stores, etc. So I have SQL links into the ERP system to extract this data and present it on the metadata card. Of course we don't burn through stock that fast, hence a daily update is fine.

    Most of the data items in the vault are CAD 3D models or drawings - it's the models that have all the metadata attached, so about 50% of the items in the vault. There's not that many of them (yet), so a workflow is potentially feasible, but it does seem... ungainly. I guess there are probably three properties that I really want to update regularly (stock size, cost, and usage rate), so that eases the load a bit further, doesn't it?

    More and more, though, I'm thinking what I should do is set up a series of value lists, linked by part number, and then re-write the property scripts so that they use the part number as a look-up to return the cost/stock size/UR.
Reply
  • Sorry, I should have put in a bit more context.

    We're using M-Files to manage our mechanical CAD files (3D models and drawings, basically, with a few other hangers-on). I'm trying to set things up as a "one stop shop" for our designers, to save us from having to rummage through the ERP system (which like all ERP systems is extremely user unfriendly), so I want to include on the metadata sheet things like how many of a component we have in stock, how quickly we burn through stock, how much it is, where to find it in Stores, etc. So I have SQL links into the ERP system to extract this data and present it on the metadata card. Of course we don't burn through stock that fast, hence a daily update is fine.

    Most of the data items in the vault are CAD 3D models or drawings - it's the models that have all the metadata attached, so about 50% of the items in the vault. There's not that many of them (yet), so a workflow is potentially feasible, but it does seem... ungainly. I guess there are probably three properties that I really want to update regularly (stock size, cost, and usage rate), so that eases the load a bit further, doesn't it?

    More and more, though, I'm thinking what I should do is set up a series of value lists, linked by part number, and then re-write the property scripts so that they use the part number as a look-up to return the cost/stock size/UR.
Children
No Data