2

We've about 100 content types. For 10 of those content types I've created a specific routing rule. The other 90 content types are catched by a routing rule with as content type our base content type "Customer Document" with an asterisk as alias. This is working, documents are routed, but there is one issue. All documents are reset to the base content type "Customer Document", no matter what the original content type was. If I create a specific routing rule for one of those 90 content types and upload as that content type, it works.

I've tried to debug the SharePoint code responsible for routing a document, but that is a big, big mess. Anyone an idea?

4
  • Do those 90 content types have required fields? Also, would you be opposed to using a workflow instead of a routing system?
    – Mike
    Commented Dec 16, 2014 at 14:09
  • Yeah they have required fields. And, why use workflows? It is working if I add a separate rule for each content type.... But that's not really flexible of course.
    – Boland
    Commented Dec 19, 2014 at 0:14
  • I understand. If a product deems useful, it should be tested thoroughly and used every which way. However, it may be a bug. Have you looked into event receivers? That would be my next option.
    – Mike
    Commented Dec 19, 2014 at 1:08
  • Thanks, but I'm not looking for other workarounds. I have a workaround (use one routing rule / event receiver). If anyone comes across this post: Call Microsoft support, it's a bug in SP.
    – Boland
    Commented Dec 19, 2014 at 2:47

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.