The data mapping functionality is a really great way to get your data into a structured table setup that you can access anywhere in Datarails or Excel. We were able to update our GL posting processes to include more detailed descriptions and map those descriptions split by delimiter to the fields we wanted in datarails. We now can instantaneously report on all of our expenses by vendor when that could not easily be done before because of the data being segregated and in different formats. Review collected by and hosted on G2.com.
There should be a simpler way to ensure that signage remains consistent across different data sources. Datarails ought to provide a clear standard for signage conventions when importing data, and it should notify users if the inputs do not follow this standard during the setup of a new data source. Additionally, Datarails should make it straightforward to adjust signage in outputs, such as reports and dashboards, as needed. For example, we wanted all our reports to display Revenues as positive numbers and Expenses as negative. Although we standardized our data mappings, we still encountered issues because working with multiple data sources with inconsistent signage required extra effort to correct and align the signs. Furthermore, when building dashboards, there was no simple way to toggle graphs so that expenses would increase from left to right above the axis. The current workaround is to create an additional amount field that converts expenses to positive values, but this approach is not ideal. Review collected by and hosted on G2.com.
