Timeline for Hard coding data during import
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 14:09 | comment | added | TRG | Thanks! Would be a cool enhancement to be able to hard code data during all imports (i.e. not just CiviContribute) but as Paul said - would need some resource! | |
| Mar 20, 2017 at 14:08 | vote | accept | TRG | ||
| Mar 15, 2017 at 2:54 | comment | added | KarinG - Semper IT | Most people will use a Payment Processor with CiviCRM and will not need to import contributions from elsewhere every month | |
| Mar 15, 2017 at 0:12 | comment | added | Paul-Tahoe | Sort of buried in this is kind of a enhancement suggestion. If one is having to import data from a payment processor every month, it would be nice not to have to add the column every month. The concept being on import you could select a financial type that all the imported contribution get. Of course, enhancements need someone to do it and it's hard to know just how many people actually do an import like this every month and would therefore use it. | |
| Mar 14, 2017 at 18:32 | history | answered | KarinG - Semper IT | CC BY-SA 3.0 |