本文介绍了是否有任何可用简单的方法来了解是否有使用API​​架构中的变化在Salesforce?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有一个 getUpdated()方式可与合作伙伴API来获取更新记录在Salesforce的每个对象名单,但有没有办法做架构同样的事情?

There is a getUpdated() method available with partner API to get the list of updated records for each object in Salesforce, But is there a way to do the same thing with Schema?

<一个href=\"http://boards.developerforce.com/t5/Apex-$c$c-Development/How-to-I-get-the-last-modified-date-of-a-custom-object-or-field/td-p/237501/highlight/false\" rel=\"nofollow\">http://boards.developerforce.com/t5/Apex-$c$c-Development/How-to-I-get-the-last-modified-date-of-a-custom-object-or-field/td-p/237501/highlight/false

上面的链接正好解释了我的问题:(无解,但!

The above link exactly explains my problem :( no solution though!

推荐答案

有趣的问题!


  1. 写在基于ANT-迁移工具,将定期下载整个的元数据,更改提交到SVN一些脚本?阅读关于<一个href=\"http://www.salesforce.com/us/developer/docs/apex$c$c/index_Left.htm#StartTopic=Content/apex_deploying_ant_retrieve$c$c.htm\"相对=nofollow>检索code 操作(没有在世界上最好的名字。但因为它接受package.xml中的配置源我相信你可以依靠它来检索对象太)。

  2. 通过自动化来。特别是企业WSDL( *)应该是很好的数据模型更改。并再次 - 你需要的东西来检测文件之间的差异

  3. 很奇怪的想法 - 你可以尝试自动化设置审计跟踪页?或手动下载CSV,然后把它交给小加工程序(甚至是Excel工作表中应该做的)。这其中实际上将列出你的变化,但格式不最适合解析了什么改变...

  1. Write some script over the ANT-based "Migration Tool" that would periodically download whole metadata, commit changes to SVN? Read about "retrieveCode" operation (not the best name in the world. But since it accepts package.xml as config source I believe you can rely on it to retrieve objects too).
  2. Automate access to https://instance.salesforce.com/setup/build/webservices.apexp. Especially the Enterprise WSDL ( https://instance.salesforce.com/soap/wsdl.jsp?type=* ) should be good for data model changes. And again - you'd need something to detect differences between the files.
  3. Really weird idea - can you try to automate screen-scraping of the Setup Audit Trail page? Or manually download the csv, then feed it to small processing program (even excel sheet should do). This one will actually list the changes for you but the format isn't best suited to parse out what was changed...

安全港等等等等

让我们期待即将推出的工装API会处理的更好。上有改进释放API,改写了EclipseForce.com IDE插件,它释放到社区婆娘......

Let's hope the upcoming Tooling API will deal with it better. There are gossips on releasing improved API, rewriting the Eclipse "Force.com IDE" plugin and releasing it to the community...

这篇关于是否有任何可用简单的方法来了解是否有使用API​​架构中的变化在Salesforce?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!