BIDS 2008 SSRS项目显示感叹号

时间：2012-07-03 19:31:14

标签： reporting-services tfs bids rdl

我创建了一个包含多个SSRS报告项目的解决方案。每个项目都包含少量报告文件（.RDL）的定义。它们分为多个项目，因为每个项目都与不同的部署目录协同工作。

我将解决方案检查到了TFS 2010.我正在为开发人员准备如何获得解决方案的文档，因此我将其备份并从工作站中删除。我在BIDS 2008中做了一个简单的“从源代码控制中打开”命令。该项目是从源代码控制中提取的，最终位于完全相同的位置，具有完全相同的文件夹结构和文件名。但是，每个项目中的每个RDL都有一个带有感叹号的锁，旁边有一个黄色图标。我正在寻找显示此图标的原因，但根本看不到它。

我已经在互联网上研究过这个问题，但是大多数事情都是指在项目之间移动文件或缺少依赖项引用。我在这里没有这些问题。

有人可以提出警告图标的原因或诊断方法吗？

2 个答案:

答案 0 :(得分：3)

我有同样的问题。我所要做的就是关闭BIDS exe而不是重新运行它。从“最近的项目”链接再次打开解决方案后，项目打开，惊叹号消失了！希望你现在也想出来了。

答案 1 :(得分：1)

首先，我为您将看到的解释正在发生的事情的xml代码量道歉。

我们在这里遇到同样的问题。我发现，无论出于何种原因，当一个新的报告文件被添加到项目中时;无论名称如何，它都将其放在解决方案资源管理器列表的末尾。

此外，它将此作为列表中的最后一个子项。一旦提交到TFS并将其拉回到xml节点仍然是相同的方式，但在您的解决方案资源管理器中，文件以正确的alpha顺序显示。但是，由于项目xml和解决方案资源管理器不同步，因此您会收到感叹号。

我发现卸载项目文件的解决方案进入并编辑xml，将元素放置在正确的alpha顺序中。

实施例

<Reports>
<ProjectItem>
  <Name>AccountGroupListing.rdl</Name>
  <FullPath>AccountGroupListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ApprovalRouteListing.rdl</Name>
  <FullPath>ApprovalRouteListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BalanceSheetWCodesReport.rdl</Name>
  <FullPath>BalanceSheetWCodesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BalanceSheetWOCodesReport.rdl</Name>
  <FullPath>BalanceSheetWOCodesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BankAccountListing.rdl</Name>
  <FullPath>BankAccountListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BankReconDetail.rdl</Name>
  <FullPath>BankReconDetail.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BankReconSummary.rdl</Name>
  <FullPath>BankReconSummary.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BasicBudgetProof.rdl</Name>
  <FullPath>BasicBudgetProof.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BillsToBeApproved.rdl</Name>
  <FullPath>BillsToBeApproved.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ChartOfAccountsListing.rdl</Name>
  <FullPath>ChartOfAccountsListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryGuideListing.rdl</Name>
  <FullPath>DoubleEntryGuideListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryPaymentProcessing.rdl</Name>
  <FullPath>DoubleEntryPaymentProcessing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryReport.rdl</Name>
  <FullPath>DoubleEntryReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryReportDetail.rdl</Name>
  <FullPath>DoubleEntryReportDetail.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>InvoiceForm.rdl</Name>
  <FullPath>InvoiceForm.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>InvoiceFormSelfSealer.rdl</Name>
  <FullPath>InvoiceFormSelfSealer.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PaymentHistory.rdl</Name>
  <FullPath>PaymentHistory.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PaymentRegisterDetailReport.rdl</Name>
  <FullPath>PaymentRegisterDetailReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PaymentRegisterSummaryReport.rdl</Name>
  <FullPath>PaymentRegisterSummaryReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>POByAccountCode.rdl</Name>
  <FullPath>POByAccountCode.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>POPaperlessDistibutions.rdl</Name>
  <FullPath>POPaperlessDistibutions.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PORequiresPayment.rdl</Name>
  <FullPath>PORequiresPayment.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ProrationListing.rdl</Name>
  <FullPath>ProrationListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PurchaseOrderForm.rdl</Name>
  <FullPath>PurchaseOrderForm.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PurchaseOrderFormLineItems.rdl</Name>
  <FullPath>PurchaseOrderFormLineItems.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ReceivablesReport.rdl</Name>
  <FullPath>ReceivablesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RequisitionApprovalAudit.rdl</Name>
  <FullPath>RequisitionApprovalAudit.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RequisitionForm.rdl</Name>
  <FullPath>RequisitionForm.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RequisitionProof.rdl</Name>
  <FullPath>RequisitionProof.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RevenuesReport.rdl</Name>
  <FullPath>RevenuesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>UnapprovedRequisitions.rdl</Name>
  <FullPath>UnapprovedRequisitions.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>VoidPayments.rdl</Name>
  <FullPath>VoidPayments.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>LoriTest.rdl</Name>
  <FullPath>LoriTest.rdl</FullPath>
</ProjectItem>

注意LoriTest.rdl是如何在VoidPayments.rdl文件之后发布的。如果你看一下我的图片，图标上是否有感叹号。

Solution Explorer

我的同事添加了这个文件，提交了更改并将其删除。该文件在解决方案资源管理器中以正确的顺序显示，但在实际项目xml中不显示。如果我关闭BIDS并重新打开标记消失，但项目文件仍然搞砸了，UNTIL我添加了一个新文件。现在我的文件放在最后，loritest.rdl在列表中向上移动到正确的alpha顺序。

看我的第二张照片。

Solution Explorer 2

现在看一下项目文件代码

<Reports>
<ProjectItem>
  <Name>AccountGroupListing.rdl</Name>
  <FullPath>AccountGroupListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ApprovalRouteListing.rdl</Name>
  <FullPath>ApprovalRouteListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BalanceSheetWCodesReport.rdl</Name>
  <FullPath>BalanceSheetWCodesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BalanceSheetWOCodesReport.rdl</Name>
  <FullPath>BalanceSheetWOCodesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BankAccountListing.rdl</Name>
  <FullPath>BankAccountListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BankReconDetail.rdl</Name>
  <FullPath>BankReconDetail.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BankReconSummary.rdl</Name>
  <FullPath>BankReconSummary.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BasicBudgetProof.rdl</Name>
  <FullPath>BasicBudgetProof.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>BillsToBeApproved.rdl</Name>
  <FullPath>BillsToBeApproved.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ChartOfAccountsListing.rdl</Name>
  <FullPath>ChartOfAccountsListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryGuideListing.rdl</Name>
  <FullPath>DoubleEntryGuideListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryPaymentProcessing.rdl</Name>
  <FullPath>DoubleEntryPaymentProcessing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryReport.rdl</Name>
  <FullPath>DoubleEntryReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DoubleEntryReportDetail.rdl</Name>
  <FullPath>DoubleEntryReportDetail.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>InvoiceForm.rdl</Name>
  <FullPath>InvoiceForm.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>InvoiceFormSelfSealer.rdl</Name>
  <FullPath>InvoiceFormSelfSealer.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>LoriTest.rdl</Name>
  <FullPath>LoriTest.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PaymentHistory.rdl</Name>
  <FullPath>PaymentHistory.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PaymentRegisterDetailReport.rdl</Name>
  <FullPath>PaymentRegisterDetailReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PaymentRegisterSummaryReport.rdl</Name>
  <FullPath>PaymentRegisterSummaryReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>POByAccountCode.rdl</Name>
  <FullPath>POByAccountCode.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>POPaperlessDistibutions.rdl</Name>
  <FullPath>POPaperlessDistibutions.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PORequiresPayment.rdl</Name>
  <FullPath>PORequiresPayment.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ProrationListing.rdl</Name>
  <FullPath>ProrationListing.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PurchaseOrderForm.rdl</Name>
  <FullPath>PurchaseOrderForm.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>PurchaseOrderFormLineItems.rdl</Name>
  <FullPath>PurchaseOrderFormLineItems.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>ReceivablesReport.rdl</Name>
  <FullPath>ReceivablesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RequisitionApprovalAudit.rdl</Name>
  <FullPath>RequisitionApprovalAudit.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RequisitionForm.rdl</Name>
  <FullPath>RequisitionForm.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RequisitionProof.rdl</Name>
  <FullPath>RequisitionProof.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>RevenuesReport.rdl</Name>
  <FullPath>RevenuesReport.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>UnapprovedRequisitions.rdl</Name>
  <FullPath>UnapprovedRequisitions.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>VoidPayments.rdl</Name>
  <FullPath>VoidPayments.rdl</FullPath>
</ProjectItem>
<ProjectItem>
  <Name>DerekTest.rdl</Name>
  <FullPath>DerekTest.rdl</FullPath>
</ProjectItem>

我发现你需要做的就是在你之后，这意味着添加新文件的人需要做的是添加新的报告文件，卸载项目文件并直接编辑项目文件以放置以正确的顺序提交文件。您不必绝对执行此操作，但如果您在提交之前未执行get操作，则当多个人正在处理添加报表时会遇到问题，因为它们会在项目文件中被覆盖，但它们会报告，存在于源代码管理中。

希望这有助于解释发生了什么。我还没有真正找到解决方案。我的想法是创建一个脚本或VS插件来修复排序问题。您认为Microsoft会注意到VS / BIDS中的这个错误，并且有一个修补程序，但我还没有找到它。

相关问题
最新问题