@matt.watters You might be able to achieve what you want bysimply creating links [.url files] or shortcuts [.lnk files] to the external files set up above file extensions as accepted Files types in Docman (Basic Data/EDM Basic) and finally check in the links/shortcuts created in step 1! Now you can simply click the View button to see the external file (Note! Clicking Edit will check out the link/shortcut file itself and not the external file. But what I assume from your use case you would not expect to maintain/edit the files from IFS anyway.)/Erik
@NMALKI Hi,Regarding adding data from IFS into an Excel document there is a good base example in the Online Documentation (F1) reached from Basic Data/Macros Basic that you can build upon. In my example I will assume the Excel Application object (oXl) has been created according to that base example. I will also assume the rest of the supporting code is known and used.In the Online Documentation, the example shows how to use row and column indexes together with the Cells() method. But to relate to your question about using something similar to Quick Parts/Fields in Microsoft Word I will use the Range() method instead in my example.To set up the similar part to a Fields [MS Word] you should use the Name Manager (under Formulas) in Excel for your template. There you define Names for each cell you want to address. (I will not go into things like Scope, i.e. context validity of the Name between sheets and workbook here.)Example:Public Sub Test() Open_Excel Write_To_Range "MyRange", "D
Why do you ask though? You know very well where to look for the PL/SQL code that creates this list in the first place :) Thanks Mathias!Nice to see you’re still at the Docman helm delivering quick and nice answers :)Even though approaching the task assuming it was all “hidden” in a VB Dictonary I overlooked that “.Key” was the key here :)Yes I know the database method :) But your code will be helpful when developing solutions based on actual values and when debugging (showing all attributes and their values in one go)./Erik
Hi Mathias and macro enthusiasts, Sometimes it is useful to have the complete list of attributes and their values. I have tried to find a way to loop through them but to no avail so far.In the User documentation there is a good example that can be used to loop through and list all available attributes for connected objects. Is there a way to do something similar for the “standard” document attributes?Thanks,Erik
Can you create a request on the idea wall, Erik? Good idea! But as a customer it doesn’t seem possible to access the Idea wall. Is that correct?
… Above, I *think* two of the keys actually have the *value* “*”, but that is just a guess. Some objects allow it, I think. As for your idea: perhaps. The risk, of course, is that you get multiple hits in the “source” if you do not specify all the keys. In some cases it will work, in others, it won’t. Of course, we do support multiple hits, but only when you write a PL/SQL method/function to do the transformation. When would you want this? ... Thanks for your quick response, Mathias!You are right, it seems the two keys actually have the value “*” after having tested this a little bit more.Still it would be great if the idea that came from this could be an option in standard. Getting multiple hits would not be a problem (possible string overflow to be considered of course), because that is what I am looking for :)What I would like is to be able to see all document connected to e.g. the Purchase Order Lines when having focus on the Purchase Order Header without having to make a custom
Hi @Mathias Dahl,This was a really good and interesting thread!The following (an excerpt from one of your posts above) gave some hope that you could use ‘*’ as values for keys that are not available on the target. E.g. when you want to show documents connected to the requisition lines also on the header.The code example you show returns the key_refs even though two of the keys are sent in as ‘*’ values. That worked fine when I tested it in a database tool. But I didn’t get it to work when setting up the OCT.select * from table (doc_reference_object_api.Get_Key_Refs('ShopOrd', 'ORDER_NO=200142^RELEASE_NO=*^SEQUENCE_NO=*^')); Could it be a candidate for future enhancements to make it possible to use ‘*’ as values when mapping keys? :)Best regards,Erik
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.