# Comment field differently scaled in preview mode then in Regular view (cosmetic impact on recon)

**URL:** <https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675>\
**Category:** Templates\
**Created:** [February 17, 2020, 10:26am UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675 "2020-02-17T10:26:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![rumoerman](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@rumoerman](https://community.silverfin.com/u/rumoerman)\
**Post date:** [February 17, 2020, 10:26am UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675/1 "2020-02-17T10:26:18Z")

</div>

Dear,

On a reconciliation, we often implement review comments. It is handy to be able to read the review comment in the regular view without scrolling with the cursor in it.

On the preview, the review comment is less nice presented. However, when the reviewer needs to add something to the comment he needs to click back to the regular view. Scroll to the line to edit a review, which is not handy to read in that representation.  
If we would add a different sizing, we lose the overview in the recon.

**Is there a way to make the regular view scale like the preview in a reconciliations?**

Thanks

Best regards

Ruben Moerman

The end of the comment not visible in the regular view  
 ![regular view](https://canada1.discourse-cdn.com/flex030/uploads/getsilverfin/original/2X/6/69493e73f989a80feb2b704c43f023d1ca8c3883.png)  
On the preview it is …  
 ![Preview](https://canada1.discourse-cdn.com/flex030/uploads/getsilverfin/original/2X/9/9380ed2941b3dbd03c9b050f7806280b2bd5baa9.png)

It seems to scale differently …

---

<div class="post-metadata">

**Author:** ![borjaGonzalez](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/borjagonzalez/32/825_2.png) [@borjaGonzalez](https://community.silverfin.com/u/borjaGonzalez)\
**Post date:** [February 17, 2020, 10:33am UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675/2 "2020-02-17T10:33:22Z")

</div>

Hi Ruben,

I think a solution might be using the **text** data type for the comments as this will get you a bigger input box and expand the text. Try this:

```auto
{% input custom.test.comment as:text %}

```

Best,  
Borja

---

<div class="post-metadata">

**Author:** ![rumoerman](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@rumoerman](https://community.silverfin.com/u/rumoerman)\
**Post date:** [February 17, 2020, 10:53am UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675/3 "2020-02-17T10:53:41Z")

</div>

Hi Borja,

Thank you for your feedback. I updated the recon, but now the rows seem to be heigher then before and the overview on the recon is now a bit lost.

Can we fix this by adding sizing?

{%input … size:maxi %}

I fail getting one line on that text for an empty comment

Best regards

Ruben Moerman

---

<div class="post-metadata">

**Author:** ![borjaGonzalez](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/borjagonzalez/32/825_2.png) [@borjaGonzalez](https://community.silverfin.com/u/borjaGonzalez)\
**Post date:** [February 17, 2020, 11:04am UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675/4 "2020-02-17T11:04:09Z")

</div>

Hi Ruben,

Could you send me a print screen for that and the full code for the table please?

Thanks,  
Borja

---

<div class="post-metadata">

**Author:** ![rumoerman](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@rumoerman](https://community.silverfin.com/u/rumoerman)\
**Post date:** [February 17, 2020, 12:28pm UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675/5 "2020-02-17T12:28:09Z")

</div>

Hi Borja,

A small code sample where you will understand the need for it:

 ![regular view](https://canada1.discourse-cdn.com/flex030/uploads/getsilverfin/original/2X/5/554fa0c46c80013488cf3c64e25b48d1fca8ce7f.png)

From a previous post in another topic I also saw that working with type text solves that issue. Nevertheless, we still have a cosmetic issue on the hight of the reocns then …

The code snippet is:

| | Numbers 2019 | Numbers 2020 | comment |  
|-------------------------|--------------:|--------------:|:--------+  
| data line 1 | {% input custom.figure.someinputfor2019 as:currency %} | {% input custom.figure.someinputfor2020 as:currency %} | {% input custom.somereviewinput.somevalue as:string %} |  
| **other insight**  
|\_ _|_ **Numbers 2019** _|_ **comment** _|_ \_|  
| data line 1 | {% input custom.figure.someotherinputfor2019 as:currency %} | {% input custom.figure.reviewinputsecondline as:string %} | |

Best regards

Ruben Moerman

---

<div class="post-metadata">

**Author:** ![borjaGonzalez](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/borjagonzalez/32/825_2.png) [@borjaGonzalez](https://community.silverfin.com/u/borjaGonzalez)\
**Post date:** [February 17, 2020, 1:29pm UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675/6 "2020-02-17T13:29:29Z")

</div>

> [@rumoerman](#):
>
> | | Numbers 2019 | Numbers 2020 | comment |  
> |-------------------------|--------------:|--------------:|:--------+  
> | data line 1 | {% input custom.figure.someinputfor2019 as:currency %} | {% input custom.figure.someinputfor2020 as:currency %} | {% input custom.somereviewinput.somevalue as:string %} |  
> | **other insight**  
> |\_ _|_ **Numbers 2019** _|_ **comment** _|_ \_|  
> | data line 1 | {% input custom.figure.someotherinputfor2019 as:currency %} | {% input custom.figure.reviewinputsecondline as:string %} | |

Hi Ruben,

I know what you mean. This code below will work but you still have the comment box slightly higher than the rest:

```auto
{% stripnewlines %}
| 
| Numbers 2019
| Numbers 2020
| Comment
{% newline %}
|--------
|--------:
|--------:
|:--------+
{% newline %}
{% fori item in custom.numbers %}
  | {% input item.data_line %}
  | {% input item.numbers_2019 as:currency_dc %}
  | {% input item.numbers_2020 as:currency_dc %}
  | {% input item.comments as:text %}
  {% newline %}
{% endfori %}
{% endstripnewlines %}

```

If that’s not a good solution for you, I would recommend making the last column wider and remove the text data type so that you can see more of the input box. Something like this:

```auto
{% stripnewlines %}
| 
| Numbers 2019
| Numbers 2020
| Comment
{% newline %}
|----20%----
|----15%----:
|----15%----:
|:---60%-----+
{% newline %}
{% fori item in custom.numbers %}
  | {% input item.data_line %}
  | {% input item.numbers_2019 as:currency_dc %}
  | {% input item.numbers_2020 as:currency_dc %}
  | {% input item.comments %}
  {% newline %}
{% endfori %}
{% endstripnewlines %}

```

Hope that makes sense,  
Borja

---

<div class="post-metadata">

**Author:** ![rumoerman](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@rumoerman](https://community.silverfin.com/u/rumoerman)\
**Post date:** [February 18, 2020, 3:51pm UTC](https://community.silverfin.com/t/comment-field-differently-scaled-in-preview-mode-then-in-regular-view-cosmetic-impact-on-recon/1675/7 "2020-02-18T15:51:44Z")

</div>

Thanks

Ruben Moerman