Can’t Export or Copy my system – Market Place issue
Forums › ProRealTime English forum › ProRealTime platform support › Can’t Export or Copy my system – Market Place issue
- This topic has 7 replies, 2 voices, and was last updated 2 years ago by Nicolas.
-
-
01/06/2022 at 10:14 AM #184716
Hello @Nicolas,
I suppose this is no secret. But it if is, please feel free to delete.
After a bit of investigation why I couldn’t export or copy my system any more (compare the normal situation in attachment 1 vs the situation in attachment 2), I found that this is caused by the usage of a MarketPlace-bought (in this case) Indicator.
And you know what ? at the moment of implementing this Indicator I already had the idea of copying to others and how to prevent that. So I can surely imagine that this is on purpose. But it is not much convenient …I think you will know – but others should know too – that if you want to make a safety copy / export of a system using a MarketPlace tool,
- the call of the tool must be commented-out;
- the returned variables from the tool must receive dummy values (easy to do by standard in advance of the call, once you know about it);
- the PRT platform must be closed;
- after restarting PRT, the the copy or export functionality is available again.
I can imagine I missed the guidelines for this, and in that case can you kindly let know where this can be overlooked ?
N.b.: For the Export I can imagine all the good reasons to perform as it’s done. But for Copy I am not so sure ?
Thanks a lot,
Peter01/06/2022 at 10:21 AM #184720You can copy/paste a readable code anywhere you want. But it is obvious that you will not get the hidden code by just copy/pasting and that’s what you do, by just exporting a code without the call indicator (because commented out), which is the hidden code.
At the end, you are just able to export a classic code, because there is no more external private dependencies.
I have not tested, but I think the export button should also be there without a restart, just validate the code, close it and re-open it.
01/06/2022 at 10:39 AM #184727I am not sure I understand …
So I have my own code. This exports fine.
Now I call a bought Indicator (with encrypted/hidden code).1R1 = call "$XX.YY AB Patterner.Z" [1, PPercent, 0, 1.414, 1, 15, 1, 1, 1, BOInd]and as soon as that’s in, I can’t export my OWN code any more.
Is that what you are saying ?
If Yes, then I repeat that I could expect something like that even before it happened to me. But people should know about it.Also, personally I don’t see why even a Copy is not allowed (this is to my own environment with my own already private dependencies ?). It already is quite a hell to prepare a system for Live (remove Graph stuff, Optimisation variables) – not your fault. But this really will be too inconvenient. And that in an environment where one loses his changes once per week to begin with – also not your fault.
01/06/2022 at 10:54 AM #184732By default, you can’t export itf files with CALL indicators with unique import, it was the case way back before the marketplace. Products from the marketplace are the same, they are sort of “unique import itf file”, so the behavior is the same as before, and as expected I would say 🙂
While I perfectly understand you’d like to make backup of your codes with the export button, it is normal that you can’t export a file which embed file(s) that was/were made for an unique installation only.
01/06/2022 at 10:58 AM #18473301/06/2022 at 11:03 AM #18473401/06/2022 at 11:22 AM #18474001/06/2022 at 1:47 PM #184757 -
AuthorPosts
Find exclusive trading pro-tools on