Timeline for CiviBanking - Skip certain payment entries when importing
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 17, 2021 at 13:31 | answer | added | Björn Endres | timeline score: 4 | |
| Aug 10, 2021 at 19:09 | answer | added | Flying | timeline score: 0 | |
| Aug 7, 2021 at 17:49 | comment | added | Mick Kahn | Looking a bit more at the extension, I don't think its possible. CiviBanking is an extension to CiviCRM so if you really don't want it in CiviCRM at all then you will need it before importing the file. A quick look at the extension doesn't seem to have any speciific CiviBanking permissions so you can't limit to a specific user, which might be acceptable. But someone properly familiar with the extension may know more so I won't call this a answer yet. Hope there is a way. | |
| Aug 7, 2021 at 9:16 | comment | added | Detlev Sieber | Thanks for your answer! However, this would work, but in this case is not enough: The bank statements contain some payments, that should never be stored within CiviCRM because they shall not be visible to unauthorized people. (i.e. CiviCRM users with access to CiviContribute and CiviBanking, but with no access to salary information). | |
| Aug 6, 2021 at 8:12 | comment | added | Mick Kahn | Thanks for drawing my attention to Civibanking - looks very useful. From a quick look at the user guide docs.civicrm.org/banking/en/latest/user-guide the Analysing Stage gives an example of "the payment has nothing to do with CiviCRM" which is what I think you want. | |
| Aug 6, 2021 at 7:52 | history | asked | Detlev Sieber | CC BY-SA 4.0 |